Skip to content
Sign in Submit a tool

UTM Tagging and Attribution for Launch Traffic

Analytics · 9 min read ·

Tag every launch link so you know which channel brought which visitor. A naming scheme, a build routine and the traps that corrupt attribution data.

Illustration: Dark panel showing a URL broken into coloured segments with labels for source, medium and campaign, monospaced type, neon highlights

On launch day, traffic arrives from everywhere at once. A post on one platform, an email, a directory entry, a message from a friend, a mention in a newsletter. If you cannot tell which of them sent which visitor, you cannot learn anything about what worked. UTM tagging is the unglamorous practice that solves this, and it only works if it is done consistently.

This article explains the parameters, a naming scheme that scales and the mistakes that quietly corrupt your data.

What UTM parameters are

UTM parameters are short labels added to the end of a link. When someone clicks it, your analytics tool reads the labels and records where the visit came from. Google's analytics help lists these parameters: utm_id for a campaign identifier, utm_source for the referrer, utm_medium for the marketing channel, utm_campaign for the product or promotion name, utm_source_platform for the platform that directed the traffic, utm_term for a paid keyword and utm_content to distinguish different creatives within a campaign.

Two other parameters, utm_creative_format and utm_marketing_tactic, are listed but noted as not currently reported, so they add no value to your reports.

The three you must use

Google's guidance says that when you add parameters to a URL you should always use utm_source, utm_medium and utm_campaign, and recommends adding utm_id and utm_source_platform when you set any parameters. Treat those as a floor.

Practical meanings:

  • utm_source: who sent the visitor. For example a newsletter name, a directory or a social platform.
  • utm_medium: the kind of channel. For example email, social, directory, referral, community.
  • utm_campaign: the launch or promotion. For example a short code for this launch.
  • utm_content: which placement or variant. For example header link versus footer link.
  • utm_id: a stable identifier for the campaign, useful for joining data.

Naming conventions

The single biggest cause of useless attribution data is inconsistent naming. Google's guidance recommends consistent, lowercase naming across fields, unique values for distinct platforms and matching campaign names exactly, to avoid fragmentation.

Write the scheme down before you tag anything.

Rules:

  1. Lowercase only. "Email" and "email" are different values.
  2. No spaces. Use hyphens or underscores, and choose one.
  3. Short, readable, stable. Names you can recognise in a report six months later.
  4. One value per platform. Do not combine two platforms in one source.
  5. A fixed list of media. Agree the permitted values in advance.
  6. A campaign naming pattern. For example product-short-name plus launch plus year.

Example scheme:

  • utm_medium values: email, social, directory, community, referral, partner.
  • utm_source values: the specific sender, named in lowercase.
  • utm_campaign: the product name plus the launch code.
  • utm_content: placement or variant, such as header, footer, first-comment or reply-link.

Keep the list in a shared document and update it only deliberately.

Do not hand-type tags. Create a spreadsheet with columns for destination, source, medium, campaign, content and a formula that joins them into a final URL, with the parameters properly separated and encoded. Review the sheet before launch. Share the tagged links from the sheet, and nowhere else.

Advantages: consistency, a record of every link used and a ready list for auditing later.

Where to tag

Tag any link you control and share externally.

  • Email links.
  • Social posts and bios.
  • Your community posts.
  • Links you give to partners and helpers.
  • The link you submit to a directory, where permitted.
  • Newsletter sponsorships or mentions you arrange.

Do not tag where the platform will strip or rewrite the link, or where it is against the rules. Always read the platform's guidance. Where you cannot tag, rely on referrer data and, if necessary, on a short redirect you own.

What not to tag

Internal links. Tagging a link between two pages on your own site can overwrite the original source of a session and make a visit look as if it came from your own page.

Organic search. Do not tag links that search engines index.

Links in places that already pass reliable referrers, if you do not need the extra detail.

Links shown to the public in a way that exposes your internal naming unless that is fine.

Time of launch: test before you trust

Before launch, click each tagged link from a clean browser and watch the session appear in your analytics real-time view with the right source, medium and campaign. Test on a phone as well. Some in-app browsers and redirects drop parameters. Fix any that fail by choosing a different link style.

Landing pages and events

Attribution is only as useful as the events that follow. Define key events: landing, pricing view, sign-up, activation, demo request. Make sure these events fire and that the session's source is stored with the sign-up, for example in a hidden field or in your database, so it can be read later when the person becomes a customer. Analytics tools often discard sessions after a period, whereas your own database does not.

Reading the data

After launch, build a small table.

Source Medium Visits Sign-ups Activations
each source each medium counts counts counts

Compute ratios: sign-up rate and activation rate by source. Look for sources that bring few visits but good activation. Beware small numbers. A channel with ten visits cannot support strong conclusions.

Attribution limits

UTM data is helpful and incomplete.

  • Direct traffic includes people who typed the address, clicked an untagged link or came from an app that strips referrers.
  • Dark social, such as private messages, often arrives untagged.
  • Multiple touches: someone may see you three times before signing up. The last tagged click gets the credit by default.
  • Cross-device journeys: the person who reads on a phone and signs up on a laptop looks like two people.
  • Ad blockers and privacy settings may block measurement.

Because of this, treat attribution as directional. Complement it with a simple question on your sign-up form or in your first email: "How did you hear about us?" The answers often reveal channels the tags cannot see.

Common mistakes

  • Mixed capitalisation. Fragments reports.
  • Tagging internal links.
  • Inconsistent campaign names.
  • Forgetting to tag helpers' links, then wondering where traffic came from.
  • Using a different scheme in every channel.
  • Not testing.
  • Changing the scheme mid-launch.
  • Storing nothing in your own database.

An audit routine

A week after launch, export the list of source and medium values from analytics and compare it with your scheme. Any value that is not in the scheme is a mistake. Fix the data where you can, correct the sheet and record what happened. Keep the scheme document for next time.

Performance matters too

Attribution assumes visitors reach the page. Google's Core Web Vitals guidance says pages should achieve an LCP within 2.5 seconds, an INP of 200 milliseconds or less and a CLS of 0.1 or less. A slow landing page loses people before your analytics ever fire, which makes your numbers look worse and less representative.

On this site

Profiles on this site link to your website. The address shown is the one our crawler lands on after any redirects, so it may differ from the one you typed and a tag on it may not survive. The submit page starts an entry, a launch entry costs $5 and our live Ahrefs DR is published (currently 60) so you can judge the referral context. After your profile is published, check the link it shows; where the tag did not survive, the referrer in your analytics still identifies visits from this site.

A worked naming example

Suppose a team launches a log-analysis tool with the campaign code logsift-launch-2026. For an email to a newsletter list, the link carries source set to the newsletter's name in lowercase, medium set to email and campaign set to logsift-launch-2026, with content set to header-link. For a post in a developer community, source is the community's name, medium is community, the campaign is the same and content is first-comment. For a directory listing, source is the directory's name, medium is directory and content is profile-link. For a friend's message, source is partner, medium is referral and content is personal-note.

Every link shares the same campaign value, so the launch can be viewed as one campaign in reports, and the source and medium columns split it into channels. Because all values are lowercase and listed in a shared sheet, a report a year from now will still make sense. If a later launch adds a new channel, the team adds one new line to the scheme instead of improvising a spelling.

Privacy and tone

Tags are visible in the link, so do not put anything personal or sensitive in them. Avoid email addresses, names of recipients or internal codes that reveal strategy. Keep values neutral and short. Handle any measurement in line with the privacy rules that apply to your audience and be clear about it in your privacy policy.

Handing the scheme to others

If helpers, partners or colleagues will share links, give them ready-made tagged links instead of asking them to build their own. A single page of copy-and-paste links, each labelled with its audience, removes guesswork and keeps the data clean. Thank them, and tell them what you learned from the numbers afterwards, which makes them more willing to help the next time.

The takeaway

Write a naming scheme, build tagged links from a sheet, test them, keep tags off internal links, store the source with each sign-up and read the results as directional. Do that and launch week leaves you with evidence about channels.

Questions and answers

Which UTM parameters are required?
Google's guidance says to always use utm_source, utm_medium and utm_campaign, and to also include utm_id and utm_source_platform when setting any parameter.
Should UTM values be lowercase?
Yes. Google recommends consistent, lowercase naming, since different capitalisations are treated as different values and fragment reports.
Can I use UTM tags on internal links?
Avoid it. Tags on links within your own site can overwrite the original source of a session and distort attribution.
What if a platform strips parameters?
Some apps and redirects remove them. Test each channel and use a dedicated landing path or a short redirect you control as a fallback.

Sources

Related guides

Help centre