Google Ads Auto-Tagging vs Manual UTM Tagging: Which Should You Use?

Google Ads offers two ways to tell your analytics where a click came from. Auto-tagging appends a gclid parameter and lets Google's systems fill in the rest. Manual tagging means adding UTM parameters to your final URLs yourself, the same way you would for an email or a Meta ad. Google's own guidance says you can use both, which is true, but the way they interact is not obvious, and getting it wrong is a top cause of Google Ads traffic showing up as (not set) or with campaign names that do not match the account. This article explains what each method captures, how GA4 resolves conflicts, and the configuration we recommend.

How auto-tagging works

With auto-tagging enabled (the default for new accounts), every ad click lands on your page with a gclid parameter attached. The parameter itself contains no readable campaign information; it is an opaque key. When the GA4 tag sees it, GA4 asks Google Ads for the click's details and records campaign, ad group, keyword, match type, ad network, placement, and device against the session. Google Ads then uses the same key to import GA4 conversions and to attribute Google Ads conversion tags. None of this needs a change to your URLs, and it works for every campaign type including Performance Max, where you have no control over the final URL per asset.

The catch is that only Google products can read a gclid. Your CRM, your email platform, an attribution tool, or a first-party tracker sees a meaningless string. If the sales team asks which Google Ads campaign a lead came from and the only tag on the landing URL was a gclid, the answer lives in GA4 and nowhere else.

How manual UTM tagging works

Manual tagging appends standard UTM parameters: utm_source=google, utm_medium=cpc, utm_campaign=your-campaign-name, and optionally utm_term and utm_content. Anything that reads the landing URL can store them, which is the whole point. The downside is that you have to add them to every ad, and keep them in sync when campaigns are renamed. Done by hand this fails fast. Done through a tracking template it is maintenance-free.

A tracking template is a URL pattern set at the account, campaign, or ad group level in Google Ads. Using ValueTrack parameters it can insert the campaign ID, ad group ID, keyword, match type, device, and network dynamically: {lpurl}?utm_source=google&utm_medium=cpc&utm_campaign={campaignid}&utm_term={keyword}&utm_content={creative}. The final URL suffix field does the same thing for the query string alone and is simpler when you do not need redirects. Either way the tags are generated per click, never typed. Our Google Ads UTM builder produces the suffix with the right macros already in place.

Side by side

What happens when a click has both

This is where most confusion comes from. When a session arrives with both a gclid and UTM parameters, GA4 has to choose. The default behaviour is that auto-tagging wins: GA4 records the campaign, source, and medium from the Google Ads account and discards your manual values. Your utm_campaign name never appears in GA4 for that session. This is usually what you want, because the auto-tagging data is richer and because it is what Google Ads conversion import relies on.

If you need your manual values to take precedence in GA4 (for example because you run a cross-platform naming convention and want Google Ads campaigns to appear under the same names as Meta and LinkedIn), each Google Ads link in GA4 admin has a manual tagging override setting. Turning it on makes GA4 prefer the UTMs when both are present. Be aware that some auto-tagging dimensions such as keyword and match type are then lost for those sessions. For most teams the better compromise is to leave GA4 on auto-tagging and use the UTMs for the non-Google tools that cannot read a gclid anyway.

The setup we recommend

1. 1Leave auto-tagging on. It is required for GA4 to import conversions into Google Ads and for Google Ads to attribute its own conversion tag.
2. 2Link Google Ads to GA4 under Admin, Product links. Unlinked accounts are the main reason google / cpc traffic shows campaign (not set).
3. 3Add an account-level final URL suffix with UTMs using ValueTrack: utm_source=google&utm_medium=cpc&utm_campaign={campaignid}&utm_term={keyword}&utm_content={creative}. Use IDs rather than names so renames do not break history.
4. 4Leave manual tagging override off in GA4 unless you have a specific cross-platform reporting requirement and understand what you lose.
5. 5Test one landing page per campaign type with a sample gclid appended to be sure your site preserves unknown parameters through any redirects.
6. 6Store the UTMs and the gclid in your first-party tracker or CRM on arrival so that leads carry the campaign ID, and so that offline or server-side conversions can be sent back to Google Ads with the click ID attached.

Why the gclid matters beyond analytics

The gclid is also the key for offline conversion import and for enhanced conversions for leads. If a visitor clicks an ad, fills in a form, and becomes a customer two weeks later in your CRM, you can send that conversion to Google Ads by uploading the gclid captured at form time together with the conversion value. Google's newer approach, enhanced conversions for leads, uses hashed email instead of the click ID, but storing the gclid on the lead record remains the most reliable path. This is the same pattern as Meta's Conversions API and TikTok's Events API, and it is why our server-side conversion tracking guide treats click IDs and UTMs as first-party data to be captured once and reused, rather than something that lives only in the analytics tool.

Put simply: auto-tagging is for Google, manual tagging is for everyone else, and the gclid you capture on arrival is what closes the loop when the conversion happens somewhere Google cannot see. Run all three and the question of which to use stops being a question.