A UTM naming convention for an agency should be short enough that every team member follows it without checking: everything lowercase, a fixed list of utm_source and utm_medium values that match GA4's default channel groups, a structured utm_campaign pattern, and utm_content reserved for creative IDs. Let Google Ads auto-tagging do its job, use Meta's dynamic URL parameters, generate every link from one shared builder, and audit it monthly.
UTMs fail slowly. Nobody notices one person typing "Facebook" and another "facebook" until the client's GA4 report shows the same channel split across five rows, half of it landing in "Unassigned". With many clients and a rotating team, a written convention is the only thing that keeps reporting comparable across accounts and over time.
The rules that apply to every parameter
- Lowercase only. GA4 treats
Facebook and facebook as different values. One rule removes a whole class of errors.
- No spaces. Use hyphens between words and underscores between segments. Spaces become
%20 or + and get mangled by link shorteners and email tools.
- No personal data. Never put an email, name or phone number in a UTM. It ends up in analytics, which platform terms prohibit.
- Values from a list, not from memory. Source and medium come from a controlled vocabulary. Campaign follows a pattern.
- No UTMs on internal links. Tagging a link from the client's homepage to their pricing page starts a new session attribution and overwrites the real source.
Source and medium aligned to GA4 channel groups
GA4 sorts traffic into its default channel group using rules based mainly on source and medium. If your values do not match those rules, traffic falls into "Unassigned" or the wrong channel. The rules are documented by Google and occasionally updated, so check the current definitions, but the core patterns are stable:
- Paid channels expect a medium that matches the paid pattern, such as
cpc, ppc or a value beginning with paid.
- Paid Social and Organic Social depend on the source being recognized as a social site, so use plain platform names like
facebook, instagram, linkedin, tiktok.
- Email expects
email as the source or medium.
- Display expects mediums like
display, banner or cpm.
- Affiliates expects
affiliate; Referral expects referral.
A starter vocabulary that maps cleanly:
| Traffic | utm_source | utm_medium | Expected GA4 channel |
| Meta paid (Facebook placements) | facebook | paid_social | Paid Social |
| Meta paid (Instagram placements) | instagram | paid_social | Paid Social |
| LinkedIn ads | linkedin | paid_social | Paid Social |
| TikTok ads | tiktok | paid_social | Paid Social |
| Microsoft Ads search | bing | cpc | Paid Search |
| Organic social posts | facebook, linkedin, etc. | social | Organic Social |
| Newsletter | newsletter | email | Email |
| Partner or affiliate | partner domain or name | affiliate | Affiliates |
| Programmatic display | network name | display | Display |
Pick one medium for paid social and stick to it across every client. Whether it is paid_social or paidsocial matters less than everybody using the same one, but verify your choice lands in Paid Social in GA4 before rolling it out.
Notice Google Ads is not in the table. That is deliberate.
Google Ads: let auto-tagging work
With auto-tagging on, Google Ads appends a gclid (or gbraid/wbraid on some iOS traffic) to every click. When the Google Ads account is linked to GA4, GA4 uses that click ID to pull the campaign, ad group and keyword details. That is more accurate than manual UTMs and needs no maintenance.
- Keep auto-tagging on. It is also required for most Google Ads conversion tracking to attribute properly.
- Never strip the gclid. Redirects, URL shorteners, some page builders and some consent setups drop query parameters. Click a live ad and confirm the gclid survives to the landing page.
- Manual UTMs are optional. Some agencies add UTMs to Google Ads for CRMs that cannot read gclid. If you do, add them through the account-level final URL suffix, use
google / cpc, and use ValueTrack parameters such as {campaignid} rather than typed names. Check in GA4 that Google Ads traffic still reports correctly afterwards.
Storing the gclid in the CRM matters more than UTMs for Google Ads leads. See CRM lead source attribution in HubSpot and GoHighLevel.
Campaign naming patterns
utm_campaign is where conventions usually fall apart, because people want to describe the campaign in words. Use a fixed segment order instead:
{objective}_{audience}_{offer}_{yyyymm}
prospecting_lookalike-buyers_free-quote_202611
retargeting_site-visitors-30d_spring-sale_202611
Rules for the pattern:
- Segments separated by underscores; words within a segment by hyphens.
- Each segment uses a short controlled list (objective:
prospecting, retargeting, brand, promo).
- Match the campaign name inside the ad platform to the UTM where you can, so reports join without a lookup table.
- Do not include the client name. The UTMs live on the client's own site and properties; the client name adds nothing and leaks between accounts when someone copies a link.
GA4 also supports utm_id for a campaign ID, which is useful when importing cost data. Add it to the builder if a client needs it.
utm_content and utm_term
utm_content distinguishes ads within a campaign. Use it for a creative ID, not a description:
utm_content=cr-0412_video_hook-b
A creative ID that also appears in the file name, the ad name and the creative tracker means you can trace a lead in the CRM to the exact asset that produced it. That is what makes creative testing measurable beyond platform metrics; see our ad creative testing framework.
utm_term was designed for paid search keywords. For Meta, many teams use it for the ad set name. Pick one meaning per platform and write it down.
Meta: use dynamic URL parameters
Meta Ads lets you set URL parameters at the ad level with dynamic values that fill in at click time. That keeps UTMs accurate when campaigns are renamed or duplicated. A common setup:
utm_source={{site_source_name}}&utm_medium=paid_social&utm_campaign={{campaign.name}}&utm_content={{ad.name}}&utm_term={{adset.name}}&utm_id={{campaign.id}}
Notes on this:
{{site_source_name}} returns short codes for the placement's site (for example a code for Facebook and another for Instagram), not the plain words. If you need GA4 to classify these as Paid Social reliably, either check how they are categorized in the client's property or hard-code utm_source=facebook and accept losing the placement split.
- Dynamic names are only as good as the names in Ads Manager. Name campaigns, ad sets and ads with the same lowercase convention so the UTMs inherit it.
- Add the parameters in the URL parameters field, not pasted into the website URL, so they apply consistently and survive edits.
- Meta adds
fbclid on its own. Capture it in the CRM as well.
The shared builder sheet
Every link should come from one builder, never be typed by hand. A shared spreadsheet is enough:
- A vocabulary tab: the allowed sources, mediums, objectives and audiences, each a data validation dropdown.
- A builder tab: columns for client, destination URL, source, medium, campaign segments, content ID, then a formula that lowercases everything, replaces spaces with hyphens and concatenates the final URL with the right
? or & depending on whether the destination already has parameters.
- A log tab: every generated link with who made it and when, so you can trace odd values later.
Keep one builder for the agency with a client column, rather than one per client. The vocabulary is what you want consistent across accounts.
Governance and audits
A convention without checks lasts about a quarter. Build in three habits:
- Onboarding: every new team member and freelancer gets the one-page convention and access to the builder before they launch anything.
- Monthly check: in each client's GA4, open a traffic acquisition report by session source / medium and by session campaign. Look for uppercase values, typos, values outside the vocabulary, and anything in Unassigned. Fix the source link, then add a note in the log.
- CRM check: look at last month's leads by
utm_source. Blank values on paid leads point to capture problems, not naming problems, and need a different fix.
Historical data in GA4 cannot be rewritten, so fix fast. Custom channel groups in GA4 can regroup messy past values for reporting, but they are a patch, not a substitute for clean links.
Special cases the convention should cover
Most UTM drift comes from channels nobody thought about when the convention was written. Decide these in advance:
- Email platforms that add UTMs automatically. Many email tools can append UTMs to every link. Either turn that off and use your builder, or set the tool's defaults to match your vocabulary. Two systems both adding UTMs produce messy duplicates.
- QR codes and print. Use
utm_medium=qr or offline with a source naming the piece (flyer, direct-mail). Point the QR code at a URL you control so the destination can change without reprinting. Check how GA4 classifies your chosen medium; anything outside the default rules lands in Unassigned unless you add a custom channel group.
- Link-in-bio and organic profiles. Tag profile links with
utm_medium=social and a campaign like profile-link so organic social traffic is separable from posts.
- Link shorteners and vanity domains. Confirm the redirect keeps query parameters. Some strip them, which also strips click IDs.
- Partner and affiliate links. Give each partner a fixed source value in the vocabulary, not whatever they choose to type.
- Sales team links. Links in sales emails and proposals should either be untagged or use a dedicated medium, so they do not inflate marketing channels.
A one-page convention you can copy
The document every team member gets should fit on one page:
- All values lowercase, hyphens within words, underscores between segments, no spaces.
utm_source and utm_medium from the vocabulary tab only.
utm_campaign follows objective_audience_offer_yyyymm.
utm_content is the creative ID.
utm_term is the keyword for search and the ad set for Meta.
- Google Ads uses auto-tagging; manual UTMs only via final URL suffix with ValueTrack.
- Meta uses dynamic URL parameters at the ad level.
- Never tag internal links. Never put personal data in a UTM.
- Every link comes from the builder and is logged.
If someone needs a value that is not in the vocabulary, they ask for it to be added rather than inventing one. That single habit keeps the list clean across years and clients.
Testing a convention before rollout
- Generate one test link per source and medium pair from the builder.
- Open each in a private window and check GA4 Realtime or DebugView for the session source, medium and campaign.
- Confirm each lands in the expected default channel group after processing.
- Submit a test lead from each and confirm the CRM fields match.
- Click a live Google ad and a live Meta ad and confirm click IDs and UTMs survive any redirects.
Common mistakes
- Mixed case, especially in source names copied from platform UIs.
- Manual UTMs on Google Ads that use made-up campaign names and conflict with auto-tagged data.
- Redirects or vanity URLs that drop all query parameters.
- UTMs on internal banners and navigation links.
- Using
utm_medium=social for paid ads, which sends paid traffic to Organic Social.
- A convention that lives in one person's head.
Where this fits
Clean UTMs are only useful if they reach the CRM with every lead. Our CRM lead attribution service sets up capture and mapping alongside the convention, and checks it as part of the conversion tracking audit.