Chapter 15 — UTM Parameters vs. Google Ads Auto-Tagging

Split channel problem

Symptom GA4 shows both google / cpc and googleads / paid for the same campaigns.

Cause Non-standard UTMs override channel logic.

Fix Standardize to utm_source=google, utm_medium=cpc.

“Where did my Google Ads campaign names go?”

Symptom GA4 reports do not show your Ads campaign naming where you expect.

Cause Some GA4 dimensions read UTM campaign; Google Ads dimensions are separate.

Fix Use UTM campaign to match your cross-channel taxonomy. Use Google Ads-linked reports for native Ads campaign names.

gclid missing

Symptom No cost data and weak keyword visibility.

Cause Auto-tagging off, or query strings stripped by redirects/shorteners/security gateways.

Fix Turn auto-tagging on. Ensure all redirects preserve parameters. If you use a shortener or gateway, allowlist gclid.

Duplicate or incorrect session attributions

Symptom Spikes in “Unassigned” or odd mediums.

Cause Typos or novel medium values.

Fix Constrain utm_medium to cpc/ppc for paid search. One cloud security team used utm_medium=paidsearch and saw “Unassigned”; switching to cpc restored clean grouping.

Non-Google ad platforms still rely on UTMs

• Microsoft Ads: msclkid exists, but GA4 still uses UTMs for source/medium/campaign.
• LinkedIn, Facebook, X: They may add their own click IDs, but GA4 uses UTMs for attribution and channel grouping.

An ABM program that splits budget across Google, Microsoft, and LinkedIn uses UTMs to standardize naming across all three. gclid only enhances Google Ads.

Minimal templates you can copy

Google Ads Final URL suffix (account level):

• utm_source=google&utm_medium=cpc&utm_campaign={campaignid}-{campaignname}&utm_term={keyword}&utm_content={adgroupid}-{matchtype}-{creative}

Microsoft Ads (where supported):

utm_source=bing&utm_medium=cpc&utm_campaign={CampaignId}-{Campaign}&utm_term={Keyword}&utm_content={AdGroupId}-{QueryString}

A data-warehousing SaaS uses these templates so the pipeline dashboard can group by “Paid Search” while the SEM team optimizes by keyword and creative.

Light operational guardrails that prevent leaks

• Standardize utm_source/utm_medium for search to “google / cpc” and “bing / cpc.”
• Ensure redirects preserve query strings (no stripping by shorteners, security layers, or server rules).
• Document where UTMs are applied (account-level suffix vs. ad-level) to avoid duplicates and drift.

Keep Google Ads auto-tagging ON for granular Ads data and cost import. Layer standardized UTMs for cross-channel attribution. Do not invent new medium values that fight GA4’s channel logic. This pairing protects both SEM performance reporting and RevOps pipeline views.