What this template is for
Campaign reports are only as readable as the labels on the traffic. Analytics tools read tagged links literally, so a medium written two ways is two mediums, and a campaign named differently in the ad platform and in the link cannot be joined without manual work. The template fixes four things at once: what each parameter carries, which values are allowed, how a campaign is named, and how the same campaign is named inside the ad account. The first three decide what GA4Google's event-based analytics platform. reports show, as the reports and dimensions guide explains; the fourth decides whether platform spend can be matched to analytics outcomes without a lookup table.
Use the template before the first tagged link leaves the building, and again whenever channel reports fill with unassigned traffic or a report has to be rebuilt because campaign names changed mid-flight. It is written to be short enough to fit on one page of a wiki and to be sent to agencies and partners as part of onboarding. It belongs beside the measurement plan template, whose segments depend on these labels arriving consistently, and it is one of the three documents in the measurement templates hub. Google's own URL builder documentation, cited in the sources, lists the parameters and their intended meaning; the vocabularies below are a convention layered on top of that documentation, not a substitute for it.
UTM parameter rules
Every parameter has one job and one format. The rules below apply to every link, every channel and every supplier without exception; the exceptions are what make reports unreadable.
| Parameter | Carries | Format rule | Required |
|---|---|---|---|
utm_source | The platform or property the click came from | Lower case; one word from the source list; no medium or campaign information | Always |
utm_medium | The kind of channel | Lower case; one value from the medium list; underscores inside a value | Always |
utm_campaign | The initiative that planned or paid for the link | The campaign name pattern below, hyphens between fields, no spaces | Always |
utm_content | The variant within the campaign: creative, placement, link position | Lower case; underscores inside; nothing already carried by another parameter | When a campaign has more than one variant |
utm_term | The paid keyword or the audience name | Lower case; omit where the platform auto-tags search | Paid search and audience campaigns only |
utm_id | A campaign identifier for joining imported cost data | Issued from the campaign register, never typed by hand | Only where cost import is used |
Three rules sit above the table. Lower case everywhere, because tools do not merge case variants. Underscores inside a value and hyphens between the fields of a campaign name, so that a reader can tell a multi-word value from a multi-field name at a glance. Letters, digits, underscores and hyphens only: no spaces, ampersands, question marks, hashes, plus signs or accented characters, all of which either break the link or encode unpredictably. Place the parameters after the page's own query string and before any fragment, and test that redirects and link shorteners pass them through to the final URL.
Allowed values for source and medium
The medium list is the heart of the convention, because channel groupingsRules that assign each visit or conversion to a channel, such as organic search or email, from its source, medium and campaign values. in analytics are rules over the medium above all. Keep it short, map every value to the channel it should land in, and treat a new medium as a governance decision rather than something a campaign manager invents.
| Medium value | Use for | Expected channel grouping | Typical sources |
|---|---|---|---|
cpc | Paid search on any engine where manual tagging is used | Paid search | google, bing |
paid_social | Any paid placement on a social platform | Paid social | meta, linkedin, tiktok, pinterest |
display | Banner and native placements bought on impressions | Display | google, the buying platform's name, a publisher's domain |
paid_video | Paid placements on video sites; paid video on a social platform takes paid_social | Paid video | youtube |
organic_video | Unpaid video posts and the links in their descriptions | Organic video | youtube |
email | Every email the business sends, marketing or transactional | newsletter, crm, transactional | |
organic_social | Unpaid posts and profile links | Organic social | linkedin, instagram, facebook |
affiliate | Partner links paid on performance | Affiliate | The partner's domain |
referral | Links placed with partners or in directories, not paid per result | Referral | The referring site's domain |
sms | Text message campaigns | Where the tool groups it; check the channel rules | sms |
qr | Printed material with scannable codes | Usually unassigned unless a custom channel is defined | print, packaging, event |
Channel groupings match patterns, chiefly in the medium, not the meaning of a value, which is why the two video values are written
paid_video and organic_video. GA4's default channel group recognises paid traffic by patterns that include a
medium beginning with paid, and sends a medium containing the word video to Organic video, so a bare video
medium would report paid placements as organic. The grouping rules also read the source, and Google changes the
default definitions from time to time, so check the current default channel group definitions in GA4 and test
each source and medium pair in the traffic report before adopting the list.
The source list is the set of values that may appear in utm_source, and it is longer than the medium
list because every platform and property is a source. Add a source when a new platform or partner starts
sending traffic; retire it when the platform does. The source should never repeat the medium: google
with cpc is correct, google_ads with paid is two mistakes. Where Google Ads auto-tagging is on, leave
paid search links untagged and let the platform's own parameter carry the detail; the
naming conventions and UTM guide explains when manual
tagging should override it.
Campaign name pattern
A campaign name is a structured string whose fields answer, in order, where the campaign runs, what it is for, what it is about and when it runs. The pattern is:
[market]-[objective]-[theme]-[period]
Each field takes a value from its own short list. Market is a country or region code, or global.
Objective is one of a few words aligned to the KPIA metric tied directly to an objective. the campaign is judged by, such as
prospecting, retargeting, leads, sales, brand or retention. Theme is the product line, offer or
message, as a single lower-case token with underscores inside. Period is the planning period the campaign
belongs to, written with the year first, as a year and quarter (2026q1) or a year and month (2026m02). Choose
one of the two formats for the whole register, because mixed formats do not sort chronologically. Optional
fields, such as a partner or a test flag, go at the end so that the required fields stay in fixed positions and a report can split the name on hyphens into columns.
Two things make the pattern work. First, the same name is used in utm_campaign and in the ad platform,
so that a campaign's spend and its on-site outcomes share a key. Second, a campaign register, a simple
table of every name issued with its owner and start date, is the only place names are created. Links are
built from the register, not typed, which is where a shared URL builder earns its keep.
Ad account naming pattern
Campaigns inside the ad platforms follow the same fields with platform-specific additions in front, so that a name tells a reader the campaign type and network before the market and objective. The pattern is:
[platform]_[campaign type]_[market]-[objective]-[theme]-[period]
The platform token identifies the account family where several are managed together. The campaign type
token names the type the platform uses, such as search, shopping, performance max, display or video, so
that reports grouped by type do not depend on parsing settings. The remainder is the campaign name
exactly as it appears in utm_campaign, so that stripping the prefix recovers the analytics key. Ad groups
and ad sets carry the theme and a targeting token; ads carry the creative variant that utm_content
records. The Google Ads naming conventions guide covers the
account-level reasoning, including how naming interacts with shared budgets and automated rules, and the
same structure transfers to other platforms with the platform token changed. The
paid social campaign build sheet applies the pattern to a Meta
build, with the campaign names and the UTM parameters filled in.
Examples
The example below shows the convention applied to one invented business across three channels, with the link, the analytics campaign name and the ad platform name side by side.
Tagged links and campaign names for Harbour Coffee Roasters
Harbour Coffee Roasters, an online coffee subscription business in the UK, runs three campaigns in the first quarter of 2026. The campaign register issues the names; the links are built from it.
| Channel | Link parameters | Ad platform campaign name |
|---|---|---|
| Paid social, prospecting | utm_source=meta&utm_medium=paid_social&utm_campaign=uk-prospecting-subscription_launch-2026q1&utm_content=video_a | meta_sales_uk-prospecting-subscription_launch-2026q1 |
| Email, retention | utm_source=newsletter&utm_medium=email&utm_campaign=uk-retention-roast_of_the_month-2026q1&utm_content=hero_banner | Not applicable; the email tool records the send |
| Paid search, sales | Auto-tagged; no manual parameters | gads_search_uk-sales-single_origin-2026q1 |
In the first month the paid social campaign records 1,840 sessions and 62 subscriptions in GA4, and the
platform reports £2,300 of spend against the same name, so the cost per subscription of just over £37 is
read without a lookup table. A partner agency sends a link with utm_medium=Paid_Social; it lands as a
second medium in the report, the register owner spots it in the weekly check, and the agency receives the
convention page with the three rules highlighted.
Common mistakes
- Mixed case.
Emailandemailare two mediums to the tool and one to the human; lower case everywhere. - Platform names in the medium.
facebookis a source; the medium ispaid_socialororganic_social. - Free text in the campaign name. Spaces, headlines and dates in random formats cannot be split into columns; use the pattern.
- Different names in the link and the platform. Spend and outcomes then live under different keys and every report needs a lookup table.
- Tagging internal links. A parameter on a link within the site starts a new attributed session and overwrites the real source; tag only inbound links.
- No register. When names are typed rather than issued, the convention lasts until the first new hire.
- Never checking the reports. The medium list in the traffic report should match the allowed list; a weekly look catches drift while it is cheap to fix.
