GA4 field guide

A UTM naming convention your reports can survive.

Choose one vocabulary before the campaign starts. Follow a launch across email, social, and partner links, then turn the same decisions into a spreadsheet and a local review policy.

Use Workbench rules to turn this convention into local allowlists and aliases, then check the full campaign batch before launch.

The three fields to require

For manual campaign tagging, require utm_source, utm_medium, and utm_campaign. Google recommends using these together so campaign traffic is identifiable in reports. Campaign ID and source platform can add useful structure; term and content should answer a specific reporting question instead of being filled by habit.

ParameterQuestion it answersExample
utm_sourceWho sent the visitor?linkedin
utm_mediumWhat type of channel was it?paid-social
utm_campaignWhich shared initiative?fall-product-launch
utm_contentWhich creative or placement?video-demo-v2
utm_termWhich paid keyword or audience?analytics-software
utm_idWhich internal campaign record?fy26-q4-017

Five rules that prevent reporting splits

1. Use lowercase for agreed naming fields

Analytics values are case-sensitive. Agree a source spelling such as facebook for new links. Keep campaign IDs exact, and review existing campaign history before changing case or separators.

2. Choose one separator

Use hyphens or underscores, then keep that choice everywhere. UTM Harbor defaults to hyphens because they remain readable in copied URLs.

3. Treat source as the platform and medium as the channel type

Use linkedin as a source and paid-social as a medium. Avoid swapping them or inventing a new medium for every platform.

4. Keep campaign names stable across channels

If email, paid search, and partners promote the same launch, reuse one campaign name. Put channel differences in source and medium, and creative differences in content.

5. Maintain aliases for imported links

Legacy sheets will contain values such as fb, facebook_ads, and paid_social. Use field-specific source or medium aliases to propose approved values. A source alias must never rename a campaign, term, content value or campaign ID. Confirm changes against campaign history before editing the input.

A practical starter taxonomy

SourceSuggested mediumUse for
googlecpcPaid Google search
newsletteremailYour owned email sends
linkedinpaid-social or socialPaid or organic LinkedIn
youtubevideoVideo descriptions and placements
partner-namereferralNamed partners and co-marketing
affiliate-nameaffiliateAffiliate links

Worked example: the same launch across three channels

Imagine a small software team announcing a new reporting feature. The landing page stays the same, but the newsletter, LinkedIn ad, and partner announcement need separate attribution. Decide the campaign name once: fall-product-launch. Treat each row as a placement, rather than naming a new campaign every time somebody copies a link.

PlacementSource / mediumCampaign / content
Newsletter hero buttonnewsletter / emailfall-product-launch / hero-cta
Newsletter footer linknewsletter / emailfall-product-launch / footer-cta
Paid LinkedIn demo cardlinkedin / paid-socialfall-product-launch / demo-card-v1
Partner announcementpartner / referralfall-product-launch / announcement

The two newsletter links differ only in content, so the team can compare placements without creating two campaign names. The LinkedIn and partner rows retain the shared campaign but use different sources and mediums. If the team works with several partners, replace partner with stable partner names and add them to the local allowlist.

A sheet that can be built and reviewed

url,source,medium,campaign,content
https://example.com/demo,newsletter,email,fall-product-launch,hero-cta
https://example.com/demo,newsletter,email,fall-product-launch,footer-cta
https://example.com/demo,linkedin,paid-social,fall-product-launch,demo-card-v1
https://example.com/demo,partner,referral,fall-product-launch,announcement

Paste these rows into the bulk builder. For repeated destinations, specify values per row rather than relying on shared defaults. Review the resulting sheet, then run the exported links through the UTM checker before release.

Make the convention enforceable on your device

  1. Open Workbench rules. Choose lowercase values and one separator. Existing reports may require underscores; keeping an established vocabulary can matter more than adopting this guide's default.
  2. List only the sources and mediums your next campaign actually uses. Start with the four placements above. An allowlist warning means a value is outside your local policy; it does not prove that the value is invalid in GA4.
  3. Add confirmed aliases, one per line, such as fb=facebook. Do not map two distinct publishers or audiences together just because their names look similar.
  4. Save the policy. Open tool pages detect saved-policy changes and clear previous results. The rules are stored in this browser on this device. They are not synchronized with teammates.
  5. Give the campaign owner a copy of the approved vocabulary and the final review CSV. A shared spreadsheet remains the team's source of truth; this tool checks a local copy.

Field-level decisions you can copy

FieldNew linksExisting links
source / mediumField-specific aliases and naming rulesPropose changes; owner approves before copying
campaign / content / term / source platformCase and separator rules, no source aliasesRetain existing spelling by default; show naming choices
Campaign IDKeep exact valueKeep exact value
Dynamic template or signed destinationBlock generic URL generationKeep original and require platform verification

Google documents that campaign IDs should match the IDs used for campaign-data imports. The lowercase and separator rules are local conventions. An allowlist warning is not proof of a GA4 error.

Decide these exceptions before bulk editing

Existing campaigns with a different spelling

If a live campaign already uses fall_launch, changing future links to fall-launch creates a second value. Choose a migration date or retain the existing spelling. A tool's cleaner proposal cannot rewrite earlier data. Record the decision alongside your campaign sheet so another person does not “fix” it again next week.

Dynamic ad-platform placeholders

A URL containing a placeholder such as a campaign macro has not yet become the final visitor URL. UTM Harbor keeps unresolved templates unchanged and excludes them from passing proposals. This detects common placeholder patterns, not every proprietary syntax. Follow the advertising platform's template rules, and inspect a fully expanded test link before auditing it here.

Default channel grouping versus your vocabulary

Your local allowlist and GA4's default channels serve different purposes. A value accepted by UTM Harbor is not guaranteed to become the channel you expect in GA4. Check Google's default channel definitions when choosing a new medium, especially for paid placements or less familiar sources. Validate the resulting channel in the actual property.

Internal navigation and sensitive values

Keep this convention for incoming campaign links. Do not casually apply it to your site's internal navigation; that can introduce misleading campaign values into measurement. Keep emails, customer IDs, private tokens, and personal information out of tracking values. URLs may be copied, logged, and shared even when you build them locally.

Use two separate checks before release

First check the sheet: required fields, naming, duplicates, preserved destination parameters, and matching campaign names across channels. Then check the actual journey: open the link, follow redirects, confirm the intended page loads, and verify attribution in your analytics property. A URL tool can perform the first check; the campaign owner must verify the second with the destination and measurement setup.

Pre-launch checklist

Download CSV template

Primary reference

Parameter definitions and Google’s current recommendations are documented in the Google Analytics URL builder documentation. UTM Harbor’s taxonomy suggestions are practical defaults, not requirements imposed by Google.