You open a client report and find three spellings of the same source and several names for one campaign. The meeting starts with spreadsheet cleanup instead of results. Another dashboard will not fix inconsistent names being sent into it.
Agree a small naming standard, then test the journey from ad link to report. UTM parameters are information added to a URL to identify traffic sources and campaigns. Google explains their relationship with traffic-source dimensions and how manual tagging differs from auto-tagging. [1]
1. Agree names before copying links
Create a dictionary of the fields and values the team uses. What goes in source? How do you distinguish video from image? Where are the client, market and offer recorded? Keep technical values consistent and explain them in plain language.
Do not squeeze every project detail into a long campaign name only to decode it each month. Link the name to a clear ID and reference record. When naming rules change, retain the meaning of the old version so historical reports remain understandable.
2. Separate client data before combining reports
Record each client’s accounts, GA4 property and CRM—customer relationship management system. Define who has access and where reporting files originate. Adding a client name to a file does not replace permissions or a checked import process.
When joining data, use keys that identify the client, platform and campaign ID together. Do not assume a campaign number in one tool is unique across every agency system. Use only the data necessary for the report.
Practical exercise: a small team dictionary
These fictional values illustrate a team convention, not values Google requires in every account.
| Field | Example | Review rule |
|---|---|---|
| Client code | agency_demo_a | Non-personal internal code |
| utm_source | meta | Value from the source dictionary |
| utm_medium | paid_social | Consistent team value |
| utm_campaign | demo_a_offer_autumn | Linked to the campaign record |
| utm_content | video_problem_v2 | Linked to the creative ID |
An illustrative test URL is https://example.com/offer?utm_source=meta&utm_medium=paid_social&utm_campaign=demo_a_offer_autumn&utm_content=video_problem_v2.
These fields describe marketing activity; they are not a place for a customer’s name, email or phone number. Google warns that URL paths, parameters and page titles can send personally identifiable information into Analytics and explains how to avoid that. [2]
3. Test the full journey, not just the URL
Open a test link through the route the ad will use and check that parameters survive redirects. Complete an appropriate test action without sending a real inquiry to sales, then inspect the values appearing in analytics and reporting.
If auto-tagging is enabled, check the actual reporting dimensions. UTM parameters do not necessarily replace all source values. An ad-platform click and a GA4 session are also different units; differing counts alone do not establish a broken link.
4. Test an error before handover
Try a sample file with another client’s code or a campaign missing from the dictionary. Does the import reject it, flag it for review, or mix it into the client’s data? Record the outcome and fix the process before using it in a real report.
Finally, appoint someone to approve new names and define how changes reach links and reports. A short dictionary, tested links and an understandable data flow leave more meeting time for campaign decisions instead of naming repairs.
Official sources
Source documentation reviewed: 16 October 2026. Features and eligibility may change; check the linked documentation before implementation.
