When Google Ads auto-tagging and manual UTM parameters coexist on the same URL, GA4 must choose which to use for attribution. Getting this wrong produces misattributed sessions, campaign dimensions with (not set), or campaign names in reports that do not match what you expected. This is a practical problem for any team running Google Ads alongside other paid channels.
How auto-tagging works
When auto-tagging is enabled in Google Ads, every ad click appends a GCLID parameter to the destination URL. GA4 uses the GCLID to query Google Ads and populate the full suite of campaign dimensions: campaign name, ad group name, keyword text, match type, ad network type. This is more precise thanmanual UTM-based attributionbecause it carries more data and maintains a live link to the Google Ads system.
GCLID vs utms: who wins
When both a GCLID and UTM parameters are present, GA4 prioritises the GCLID. UTM parameters are largely ignored for GA4 attribution. If you addutm_campaign=brand_searchto a Google Ads URL but the actual campaign is namedUK_Brand_Search_Exact, GA4 reports showUK_Brand_Search_Exact, notbrand_search.
This is intentional design: Google considers GCLID-based attribution more accurate and complete. The conflict arises when teams add UTMs to Google Ads URLs to feed non-Google attribution tools, expecting those values to also appear in GA4. The deeper question of whichattribution modelcredits the click is a separate conversation from which identifier GA4 reads from the URL.
When auto-tagging fails
If the GCLID is stripped by a landing page redirect, GA4 falls back to UTM parameters if present. If neither is available, Google Ads traffic appears as Direct. This is a consistently underdiagnosed cause ofpaid search traffic flipping into Directin your reports. Test by clicking a live ad and confirming the GCLID is still present in the final URL after all redirects.
Google Ads dimensions requiring auto-tagging
The richer Google Ads dimensions are most reliably populated when auto-tagging is active and the GA4 property is linked to Google Ads. If auto-tagging is disabled or broken, those dimensions may show up as(not set) valueseven when manual UTMs still preserve basic campaign attribution.
Want to check whether GCLID auto-tagging is working and UTMs are not overriding it unexpectedly?
Recommended setup
Enable auto-tagging in Google Ads and do not add redundant UTMs to Google Ads URLs. Let GA4 use the GCLID for richer campaign attribution. If non-Google tools need UTM data, add UTMs alongside auto-tagging knowing GA4 will use the GCLID. Ensure landing page redirects preserve the complete query string.
Diagnosing and fixing auto-tagging conflicts
Attribution conflicts between GCLID and UTMs are easy to miss because GA4 does not surface them as errors. Here is how to identify and resolve them.
Validate
- In GA4 Traffic Acquisition, filter for google / cpc sessions and check the Session campaign dimension, confirm campaign names match your actual Google Ads campaign names, not UTM values
- Click a live Google Ads ad and inspect the final landing page URL, confirm?gclid= is still present after all redirects complete
- Check whether any google / cpc sessions show (not set) in the campaign dimension, this indicates GCLID is being stripped
- In Google Ads, confirm auto-tagging is enabled in Account Settings > Auto-tagging
Fix
- If UTMs must take precedence over GCLID for GA4 attribution, enable the 'Allow manual tagging (UTM values) to override auto-tagging' setting in Admin > Data collection and modification > Data collection
- If GCLID is being stripped by redirects, update landing page redirect rules to preserve the full query string including gclid parameter
- Remove redundant UTMs from Google Ads destination URLs if the goal is accurate GA4 attribution, let the GCLID carry campaign data
- Ensure the GA4 property is linked to the Google Ads account in Admin > Product Links > Google Ads Links so GCLID resolution works
Watch for
- Campaign names showing as (not set) in Traffic Acquisition when you expect Google Ads data, indicates GCLID resolution failure
- google / cpc sessions appearing in the Direct channel after landing page infrastructure changes
- UTM campaign values appearing in GA4 for Google Ads traffic when you expect Ads campaign names, may indicate the override setting is enabled unintentionally
Auto-tagging and UTM checklist
- Auto-tagging enabled in Google Ads Account Settings
- GA4 property linked to Google Ads in Admin > Product Links
- Landing page redirects preserve GCLID parameters, verified by clicking a live ad
- Session Google Ads campaign dimension shows values in GA4 Explorations for known paid search sessions
- No google / cpc sessions showing (not set) in campaign dimension without explanation
- UTM override setting reviewed and set intentionally based on attribution strategy
Related guides
GA4 BigQuery Export Parity
Why GA4 standard reports and BigQuery export show different numbers, and which surface to trust.
GA4 vs Universal Analytics
How the data model, session definition, and attribution changed from UA to GA4.
Consent Mode: Analytics vs Ads
How Consent Mode affects GA4 data differently from Google Ads conversion tracking.
GDPR and GA4 Compliance
What your GA4 setup needs to do to meet GDPR requirements for EU and UK traffic.
Audit your GA4 UTM and attribution setup
G4 Audits checks 35 UTM and campaign integrity issues including auto-tagging conflicts, GCLID stripping, and (not set) campaign attribution.