When one campaign appears under several names, the problem begins before analysis. I treat link labels as part of publishing operations. If everyone invents their own abbreviations, data fragments; a shared vocabulary makes the resulting reports easier to interpret.
Separate the purpose of each field
Google Analytics documents source, medium and campaign parameters as a way to identify referral activity. Parameter values are case-sensitive. Within a team, I prefer lower-case values, agreed words and consistent separators.
| Field | Question answered | Example |
|---|---|---|
| utm_source | Which source sent the visit? | newsletter |
| utm_medium | What distribution type was used? | |
| utm_campaign | Which initiative does it belong to? | editorial_launch |
| utm_content | Which piece or link was used? | brief_guide |
These are examples, not a replacement for an existing reporting vocabulary. Check the current system before introducing new values. Renaming the same channel every month makes historical comparison unnecessarily difficult.
Maintain a link register
A useful starting record includes destination, source, medium, campaign, content code, owner and publication date. Selecting approved values rather than typing every field freely can reduce mistakes. Add new values to the vocabulary with a reason when they are genuinely needed.
I avoid making one person’s memory the source of truth. The system should survive a team change. The register also becomes a simple distribution inventory showing which content sends readers to which destination.
Keep personal information out of parameters
Email addresses, phone numbers, names and private customer details do not belong in campaign labels. URLs can be recorded and shared across systems. Use non-identifying content codes to distinguish versions.
The labelled URL should still lead to the same useful page. Parameters should not be relied on to create the article’s essential content. Before publication, confirm that the destination opens and that the link remains understandable in the context where it will be used.
Test the actual journey
Checking the spreadsheet is not enough. Follow the link through its intended email, profile or other placement. Do redirects preserve the intended destination? Does mobile navigation reach the correct language? Does an article link unexpectedly lead back to the homepage?
Measurement also depends on a valid Analytics setup and the applicable consent flow. Creating a labelled URL does not establish that data is being collected. Keep setup verification separate from distribution checks so a missing measurement signal is not automatically interpreted as a content failure.
Read reports with the naming system in mind
If one initiative splits across several rows, inspect spelling and missing fields before interpreting performance. Inconsistent values are a data-quality issue to resolve, not an audience insight.
I use UTM organisation to make the origin of existing publication activity understandable. A maintained vocabulary and a short pre-publication check reduce the need to reconstruct every link’s meaning at the end of the month.
A four-row link check before publication
Complete this record before a campaign link is shared. The values are illustrative and contain no customer or personal information.
| Check | Example record | Reason to hold publication |
|---|---|---|
| Destination | The guide in the intended language | Wrong language or missing page |
| Source / medium | newsletter / email | Another spelling for an existing channel |
| Campaign / content | autumn_guide / opening_link | Personal data or an unclear version name |
| Actual route | Click from the email preview to the destination | Parameters lost during a redirect |
Opening the page is only the first check. Inspect the final address, then separately check how an authorised test visit appears in measurement. URL behaviour and Analytics receipt are different tests. If data is missing, separate reporting delay, consent choice and implementation before repeatedly changing the link.
When a dictionary value changes, record the date instead of silently relabelling the old register. That preserves an explanation for differences between reporting periods. Google’s campaign documentation defines the parameter roles; the team’s naming dictionary remains an implementation choice.
Add this checklist to the release process in the digital projects guide. Use social media KPI selection to decide which question the measurement should support.