Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

Auto-Tagging

A Google Ads setting that adds a click identifier (GCLID) to every ad click's landing URL.
Analyticsplatform featureUpdated

Definition

Auto-tagging is an account-level setting in Google Ads. When it is on, Google appends a parameter named gclid, short for Google click identifier, to the final URL of each ad click. Each click gets its own value. The identifier carries no campaign names itself; it is a key that Google Ads and linked Google products can resolve into the click's details, which is why it can carry more than hand-built tags ever could.

Three systems read it. The Google tag or the conversion linker on the site stores it in a first-party cookie, so that a conversion later in the visit can be matched to the click. A linked analytics property reads it to label the session with campaign detail and cost. And a lead form can capture it into a hidden field so that the CRM holds it beside the contact. Google documents further click identifiers for some device and browser contexts, which are handled the same way.

In practice: analytics linking and CRM capture

Linking a GA4 property to Google Ads is the most common reason to check the setting. The GA4 and Google Ads integration tutorial offers to switch auto-tagging on during the link and then asks for a check that the website keeps query parameters through redirects, because a link without the identifier has nothing to join. The GA4 setup checklist repeats the check for the same reason. For conversion tracking inside Google Ads, the conversion tracking setup guide lists auto-tagging among the prerequisites and names a stripped identifier as a usual cause of conversions that appear in analytics but not in the ad account.

Lead businesses use the identifier a second time. The form stores it on the lead, the CRM keeps it as the lead moves through qualification and sale, and the outcome is uploaded back to Google Ads keyed by that identifier. That loop is an Offline Conversion Import, and the guide to connecting the CRM to ads and analytics sets out where to read, store and send the value.

Auto-tagging versus UTM parameters

UTM parameters are written by hand or by template and read directly by any analytics tool. The Google click identifier is generated automatically and only means something to Google's products. For a property linked to Google Ads, the identifier is the more complete source, carrying fields a UTM cannot hold. The UTM and naming conventions guide states the rule that follows: auto-tag where the platform and the analytics tool share an identifier, tag manually everywhere else, and do not put both on the same link without a documented reason. Where both are present, a property-level setting decides which wins, and the convention should record how it is set. Other ad platforms append their own click identifiers, but analytics does not read campaign detail from them, so their links still need UTMs.

What breaks it

  • Redirects that drop parameters. A landing URL that forwards to another address without passing the query string delivers the visit without the identifier.
  • Separate booking or checkout domains. If the visit moves to another domain before the action, the identifier stays behind unless the setup carries it across.
  • Forms that do not capture it. The visit is labelled correctly, but the lead in the CRM has no identifier to upload later.
  • Consent and cookies. Where storage is declined, the identifier may arrive but cannot be kept for a later conversion.
  • Switching the setting off. Campaign detail and cost stop reaching analytics, and traffic falls into whichever channel the referrer suggests.

The guide to why Google Ads and GA4 disagree treats these as faults to rule out before reading any difference between the two systems as a difference in counting.

Illustrative example — not a real result

Paid clicks that turned into direct visits

Copperleaf Funeral Plans moves its enquiry form to a new booking domain in March. Within a week, GA4 shows paid search sessions falling from about 1,150 a week to 140, while direct sessions rise by roughly the same amount and Google Ads still reports some 1,200 clicks. A test click shows why: the old landing pages now redirect to the booking domain, and the redirect rule rewrites the address without its query string, so the gclid never arrives. The developer changes the rule to pass parameters through and adds the booking domain to the analytics cross-domain list. The following week GA4 records 1,080 paid search sessions, and enquiries carry the identifier into the CRM again.

UTM parameters are the manual alternative, still needed for every other platform. A GA4 property linked to Google Ads is the main consumer of the identifier. The Offline Conversion Import depends on it to send sales back to the ad account, and every Attribution report that names a Google Ads campaign rests on it arriving intact.

Common confusions

  • The GCLID is not a UTM. It holds no readable campaign names; only Google's products can decode it.
  • Auto-tagging does not fix tagging elsewhere. Social, email and display links still need UTMs.
  • A working link to GA4 does not prove auto-tagging works. The link can exist while the identifier is stripped on every click.
  • Adding UTMs on top is not a safety net. It creates two sources of truth for one click.
  • Clicks and sessions are not meant to match exactly. Some gap is normal; a sudden large one points to a stripped identifier.

More terms to look up

Where this term is used

Related