Auto-tagging vs UTM conflicts
Google Ads auto-tagging appends a gclid to ad landing URLs; manual tagging adds utm_ parameters. When a link carries both, the two systems describe the same click differently and can disagree. By default GA4 gives precedence to gclid-based auto-tagging, so hand-set utm_source/medium on Ads links may not appear as expected. This page explains the precedence and how to avoid the conflict.
Two tagging systems, one link
Auto-tagging is Google Ads adding a gclid query parameter automatically; GA4 resolves it against the linked Ads account to derive source, medium, and campaign. Manual tagging is you adding utm_source, utm_medium, and friends. On a Google Ads final URL you can end up with both, describing the same click.
Precedence and how to avoid clashes
Google's guidance is to not use both on the same Ads links: if auto-tagging (gclid) and manual tagging both exist, GA4 prefers the auto-tagging values by default, so your manual utm_source/medium can be effectively ignored. There is a property setting to let manual tagging override auto-tagging, but mixing them invites inconsistency.
The clean rule: let auto-tagging handle Google Ads, and reserve manual UTMs for non-Ads campaigns (email, social, partners). Don't double-tag the same link.
- Both present: GA4 prefers gclid auto-tagging by default
- A property setting can let manual tagging take precedence
- Recommended: auto-tag Ads, manual-tag everything else
- Avoid putting gclid and utm_ on the same final URL
How it appears in analytics and logs
Ads traffic appearing as google/cpc despite manual UTMs means gclid auto-tagging won precedence; manual UTMs were overridden rather than lost in transit.
Diagnostic use case
Explain why Google Ads clicks show up under google/cpc from gclid even though the link also carried different manual utm_source/medium values.
What WebmasterID can help detect
WebmasterID reads campaign parameters from the landing URL first-party, so you can see exactly which parameters arrived and whether auto-tagging and manual tags disagree.
Common mistakes
- Adding manual UTMs to Google Ads links that already auto-tag.
- Expecting manual utm_source to override gclid without changing the setting.
- Debugging 'missing' UTMs that were actually overridden by gclid.
Privacy and accuracy notes
gclid and utm_ are URL parameters describing the campaign, not the person. Avoid placing personal data in either. This page is educational, not legal advice.
Related pages
- GCLID stripping and loss
The gclid is the Google Ads click identifier appended by auto-tagging. If anything between the ad and the page removes the parameter — a redirect that drops query strings, a CMS canonical rewrite, a link shortener, or a privacy tool — the landing page never sees the gclid and the click cannot be attributed. This page explains where gclid loss happens and how to detect it.
- UTM overwrite issues
Campaign attribution depends on which UTM values are present when a session begins. Two patterns cause trouble: a second campaigned link mid-journey can overwrite the first, and internal links that accidentally carry UTM parameters can reset attribution to an internal source. This page explains how UTM values get overwritten and how to keep internal links clean.
- Ads vs analytics discrepancies
It is normal for Google Ads and GA4 to report different conversion and click numbers for the same campaign. They use different attribution models, count conversions at different times (Ads at click time, GA4 at conversion time), define a click versus a session differently, and apply different windows and de-duplication. This page enumerates the documented reasons the two tools diverge.
- Campaign link docs
Build consistent, conflict-free campaign URLs.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.