Research Guides
UTM Naming Rules That Keep Campaign Reports Readable
A newsletter link named NovemberLaunch and another named november_launch can turn one promotion into several reporting labels. Before sending a campaign, agree on a small vocabulary and test the actual links. Cleaning up a naming plan is easier than explaining a month of inconsistent reports.
UTM parameters are labels added to a destination URL to help an analytics system identify campaign traffic. This guide offers a practical naming record, a fictional example and a pre-send review. It assumes you already manage the destination website and its analytics. It does not describe a Colquhoun.shop integration or claim that tagged links measure every visit or sale.
Start with a reporting question
Choose a question the labels should help answer. For a monthly email, that might be: “Which links in our November guide announcement brought recorded visits to the guide?” Write down the campaign owner, destination page and reporting period before creating a URL.
Keep the question modest. A label identifies a campaign value collected by your analytics setup. It does not show that someone read the whole guide, found it useful or purchased because of the email. Those outcomes need their own definitions and evidence.
Give each field one job
For a simple manually tagged email, start with these fields:
- utm_source identifies the referring publication or source, such as customer_newsletter.
- utm_medium identifies the marketing medium, such as email.
- utm_campaign names the promotion, such as guide_launch_2026_11.
- utm_content distinguishes placements or creative variants, such as top_button and footer_link.
Google's campaign URL guide explains these fields and recommends using source, medium and campaign together. It also documents additional parameters, including campaign ID and source platform. Check which are relevant to your setup instead of assuming this small email example covers every advertising integration.
Do not put the newsletter name in the medium field one week and the source field the next. That changes the meaning of a report even when the destination page stays the same.
Write the naming rules before the links
Use one approved spelling for each recurring source and medium. Choose lowercase labels, a word separator and an explicit rule for dates. For this guide's example, use lowercase letters, digits and underscores, with dates only in campaign names when they distinguish separate launches.
This is a proposed team convention, not a Google requirement. The University of Minnesota's published UTM guidelines offer a real example of an organization standardizing lowercase names and underscores. Your vocabulary should fit your own reporting needs.
Keep a short dictionary containing each allowed value, its meaning and one example. Assign someone to approve new values. “customer_newsletter” should mean the same publication next month, while a new campaign may deserve a new campaign name.
Google notes that parameter values are case-sensitive. That makes spelling and capitalization worth checking before release. Avoid treating Newsletter, newsletter and news_letter as interchangeable just because a person can recognize the intended meaning.
A fictional two-link announcement
Imagine an email announcing a downloadable planning guide. Both links lead to the same public guide page. The team approves these shared values: source customer_newsletter, medium email and campaign guide_launch_2026_11. Only content changes: top_button for the opening button and footer_link for the link near the end.
The team's link record contains two rows. Each row includes the destination, all approved parameter values, the finished tagged URL, placement, owner and review status. The labels describe the placement rather than declaring a winner in advance.
The top-button example would look like this, using a fictional example.com destination: https://example.com/guide?utm_source=customer_newsletter&utm_medium=email&utm_campaign=guide_launch_2026_11&utm_content=top_button
If the button later has more recorded sessions, the team can investigate that difference. It cannot conclude from the labels alone that button styling caused the result. Position, wording and the number of readers reaching each link may also differ. This is an observation about two placements, not a randomized experiment.
Keep personal information out of the URL
Use campaign-level labels, not a recipient's name, email address, phone number or account details. Review the whole destination address, including any existing parameters, before adding campaign fields. A harmless utm_campaign does not make an otherwise sensitive URL suitable for sharing.
Google's Analytics privacy guidance prohibits sending information it can recognize as personally identifiable and specifically warns about campaign parameters. Do not rely on a later report-cleaning step to undo exposure. Stop and ask the person responsible for measurement and privacy to review a questionable link before sending it.
Test the link that will actually be sent
Use a URL builder or a reviewed generation template rather than editing long addresses by hand. Preserve existing parameters that the destination needs. Review the finished address before opening it, then test the link from a draft or preview of the actual message.
- Confirm that the intended page opens and its main action still works.
- Check redirects and whether the campaign values reach the intended destination without unexpected changes.
- Compare source, medium, campaign and content against the approved dictionary.
- Ask the analytics owner to verify collection and the intended reporting view using the site's approved test procedure.
- Record the date, tester and outcome. Mark anything unverified rather than filling it with an assumed pass.
A visible parameter in the address bar is not proof that analytics collected it. Keep the link-function check separate from the measurement check. Do not bypass consent choices, access controls or existing privacy settings to force a test result.
Preserve existing advertising measurement
Before adding labels to paid-ad links, check whether the campaign already uses auto-tagging. Google's manual-tagging and auto-tagging documentation explains that the two approaches interact, and auto-tagged values can take precedence for traffic-classification dimensions.
Have the advertising owner approve the relevant fields and test the combination. Do not strip click identifiers or disable an existing integration merely to make the link resemble the email example. Record what was preserved and which report will be used.
Keep internal navigation out of the campaign plan
Use this plan for links bringing people to your website. For a homepage button leading to your own pricing page, discuss an appropriate interaction event with the analytics owner instead of assigning a new inbound campaign.
Avoid the outdated claim that a new UTM value always starts a new GA4 session. Google's campaign-processing documentation says a new campaign encountered during an existing session does not start another session. Newly collected values can still affect event-based attribution, which is a reason to keep on-site interaction measurement separate.
Read the report at the intended scope
Copy the exact report, date range, filters, dimension and metric into your review notes. “Campaign results” is too vague for someone else to reproduce. For a closer look at units, see Read Traffic Changes in the Right Units.
Google's traffic-source scope guide distinguishes first-user, session and event scopes. First-user acquisition and session acquisition answer different questions. Choose the scope that matches the question before comparing results; do not switch between them to find a more appealing number.
For the fictional email review, ask the analytics owner for session-scoped campaign and source/medium, plus Session manual ad content, paired with Sessions. Sessions are not a count of every email-link click.
If the labels split into unexpected rows, preserve the original export and document any grouping used in your analysis. Correct future links through the naming dictionary. Do not silently relabel historical evidence or assume changing a URL rewrites past collection.
A useful campaign handoff ends with three things: approved labels, tested links and a clearly named reporting view. That is a manageable foundation for learning from the campaign without asking its URL tags to prove more than they can.