UTM naming rules for cleaner affiliate traffic reports
Agree source and campaign names, test redirects and distinguish marketing tags from click identifiers and payable results.
A source can split across several report rows: telegram, Telegram and tg. A generic name such as test can also combine unrelated buys. Consistent tagging helps publishers compare placements and advertisers understand acquisition sources. This is an operating method, not a claim about automated AffiliateCore features.
1. Agree a dictionary before launch
Keep source, placement type, campaign, owner and launch date in a shared register. Use a stable source name for utm_source, an agreed channel type for utm_medium and an initiative code for utm_campaign. Pick one case convention and separator. Log changes rather than silently renaming a campaign during a test.
Illustrative example: utm_source=telegram, utm_medium=paid-social, utm_campaign=tr-autumn-01. These are fictional labels, not a live campaign or geographic recommendation. Analytics tools may group channels differently; map your dictionary to your system's rules.
2. Separate parameter purposes
UTM describes marketing origin. A click identifier links a visit to an event in a tracker; a campaign name does not replace it. UTM presence does not prove a conversion or establish a payout entitlement. Agree which parameters must survive redirects and which identifiers the advertiser returns in postbacks.
Do not put email addresses, phone numbers, wallets, passwords or secret tokens in tags. URLs can enter browser history, logs and third-party tools. Use agreed technical codes without personal information for detail.
3. Test the link journey
Follow a test link from placement to destination on relevant devices. Check redirects, preservation of permitted parameters, page loading and source visibility in your reporting tool. Do not append a second question mark to a URL that already has query parameters; use a URL builder. Avoid tagging internal navigation as a new external campaign without a deliberate reason.
4. Measure data quality
Weekly, measure visits missing an expected tag as a share of visits from the tagged placements being checked. Define that denominator first: direct visits and unrelated sources need not carry UTM. Log unknown values and name changes separately. Missing data due to consent, blockers or stripped parameters is not proof of fraud.
Your output is a dictionary, link register and exception list with owners. Reconcile earnings and costs only after agreeing events and periods: report reconciliation.