Digital Dan
← All posts

Google Tag Manager conversion linker tag explained: setup, cross-domain linking and cookie settings (2026)

The conversion linker tag in Google Tag Manager storing ad click information for Google Ads conversion tags

The conversion linker is a Google Tag Manager tag that reads the ad click information in your landing page address (the GCLID that auto-tagging adds) and stores it in first-party cookies on your own domain, so your Google Ads and Floodlight conversion tags can tie a later conversion back to the click. Without it, a lead on a different page than the landing page often can’t be credited to the ad. You fire it on All Pages, and you only skip it when a Google tag for the same destination already loads on every page.

Not sure your Google Ads conversions are being credited? I set up and audit conversion tracking in Google Ads, GA4 and Tag Manager. See my conversion tracking service.

What the conversion linker actually does

When someone clicks your ad with auto-tagging on, Google adds a click identifier to the landing page address, for example ?gclid=.... For some iOS traffic Google uses the gbraid or wbraid parameters instead of a GCLID. That identifier only exists in the address of the first page. The moment the visitor clicks to another page, it’s gone.

The conversion linker tag catches it on the landing page and saves it:

  • in first-party cookies named _gcl_*, such as _gcl_aw and _gcl_gs, set on the top-most domain and the root path by default;
  • in the browser’s local storage under the key _gcl_ls.

Later, when the visitor submits your form or buys, the Google Ads conversion tag reads that stored click information and sends it to Google Ads with the conversion. That’s the link between “this click” and “this lead”.

How the conversion linker works: an ad click lands on the site with a GCLID in the address, the conversion linker stores it in first-party _gcl cookies, the visitor moves to other pages where the address no longer has it, and the Google Ads conversion tag on the thank-you page reads the cookie and sends the conversion with the click information

It’s the same job the Google tag (formerly gtag.js) does when you install Google Ads with code on the page. In Tag Manager, the conversion tags themselves don’t store the click; the linker or a Google tag does.

Do you need a conversion linker tag?

Your setupConversion linker needed?
Google Ads conversion tags or Floodlight tags in GTM, no Google tag for that destination on every pageYes, on All Pages
A Google tag (or a Destination tag) for your Google Ads destination loads on every page in the containerNo, the Google tag already stores the click information
Google Ads tracked only with GA4 key events imported into Google AdsNo conversion linker needed for that; GA4 handles its own click attribution
Server-side Tag Manager sending Google Ads conversionsYes, in the server container as well

Google’s own note is that containers with Google Ads and Floodlight tags now load a Google tag first, unless a connected Destination tag exists. In practice I still add the conversion linker in almost every GTM container I set up. It costs nothing, and it removes any doubt about whether the click information is stored on every page, including pages where the Google tag is missing because of a trigger mistake.

If you’re still deciding between Tag Manager and the Google tag in code, I compare the two in Google Tag Manager vs the Google tag (gtag.js).

How to set up the conversion linker in Google Tag Manager

  1. In your GTM container, go to Tags and click New.
  2. Click Tag Configuration and choose Conversion Linker.
  3. Leave the default settings for a single-domain website. (Cross-domain and cookie options are covered below.)
  4. Click Triggering and choose All Pages.
  5. Name the tag clearly, for example “Conversion Linker – All Pages”, and click Save.
  6. Test it in Preview (steps below), then Submit and publish the container.

Which trigger? Google recommends All Pages in most cases, so the linker is active on any page someone could land on from an ad. You can limit it to specific landing pages, but that’s how clicks get lost when someone builds a new landing page and forgets the trigger. Some people prefer Initialization – All Pages, which fires before the regular page view triggers; that also works, as long as it’s on every page. What matters is that it fires on the landing page before the visitor leaves it.

Linking across domains

If the visitor clicks your ad on example.com and converts on another domain, for example a booking tool at example-booking.com or a separate checkout domain, the cookies on the first domain can’t be read on the second. Cross-domain linking solves that: the linker adds the click information to links pointing at the other domain (in a _gl parameter), and the conversion linker on the other domain reads it and stores it again.

The settings, in the Conversion Linker tag:

  1. Tick Enable linking across domains. This lets the tag handle incoming links that carry the linker parameter.
  2. In Auto Link Domains, list the other domains, separated by commas (for example example-booking.com). Links to those domains get the parameter added.
  3. URL Position: leave it on Query Parameter (the default). Use Fragment only if the other site’s server strips unknown query parameters.
  4. Decorate Forms: tick it if the visitor moves to the other domain by submitting a form (for example a form whose action points at the booking domain). It only works with URL Position set to Query Parameter, because some browsers drop the fragment from form submissions.
  5. Put a Conversion Linker tag with the same settings in the container on the other domain too. Both sides need it.

Two things to keep in mind:

  • Subdomains don’t need this. By default the cookies are set on the top-most domain, so www.example.com and book.example.com already share them.
  • GA4 has its own cross-domain setting. In GA4 it’s set on the Google tag, under the data stream’s tag settings (Configure your domains). Set up the domains in both places if you track the journey in GA4 as well.

You rarely need this. Google lists three reasons: you already have cookies with the same names, you need more than one set of click cookies, or you want to stop ad click data being shared across subdomains.

  1. In the Conversion Linker tag, tick Override cookie settings.
  2. Name prefix: the default is _gcl. If you change it, every tag that reads these cookies must use the same prefix (see below).
  3. Domain: by default the highest-level domain that allows cookies. Set it only to limit the cookies to a lower-level domain, for example one subdomain.
  4. Path: by default the root. Set it only to limit the cookies to one directory.

If you change the prefix, open each Google Ads conversion tag (and Floodlight tag) that should read these cookies, and in its Conversion Linking section set the same Cookie Prefix. The same section has Enable Conversion Linking, on by default; turning it off stops that tag using the stored click information, which you almost never want.

In the accounts I audit, a changed prefix on the linker and the default on the conversion tags is one of the quieter ways to lose conversions: everything fires, nothing errors, and the conversions arrive without the click information.

The conversion linker has built-in consent checks for ad_storage. With Consent Mode v2 in place:

  • ad_storage granted: the linker stores the click information in cookies as usual.
  • ad_storage denied: no new advertising cookies are set, so the GCLID isn’t stored in a cookie.
  • URL passthrough: you can let the click information travel between pages in the page address instead, while ad_storage is denied. In Tag Manager, Google’s instruction is to tick Enable linking on all page URLs in the Conversion Linker tag (in code it’s url_passthrough). It only works for links within the same domain and only when there’s a click identifier in the address.

Don’t add a separate consent trigger or blocking trigger to the conversion linker to “make it compliant”. Its built-in checks already respect the consent state, and an extra trigger usually means it doesn’t fire on the landing page at all, when the GCLID is there. If you use advanced consent mode, Google can still model conversions from visitors who declined.

How to test the conversion linker

  1. In GTM, click Preview and open your website with a test parameter added, for example https://www.example.com/?gclid=test123.
  2. In Tag Assistant, check that Conversion Linker fired on the first page.
  3. In your browser’s developer tools, open Application → Cookies for your domain and look for a _gcl_aw cookie containing test123.
  4. Click to another page and confirm the cookie is still there.
  5. For cross-domain linking, click a link to the other domain and check that the address carries a _gl= parameter, and that a _gcl_aw cookie appears on the second domain.
  6. If you use a consent banner, repeat the test after accepting and after declining, so you know what happens in both cases.

A test GCLID won’t produce a real conversion in Google Ads. It only proves the click information is stored. To prove the full chain, use a real ad click and a real conversion, then wait for Google Ads to report it.

Common mistakes

  1. No conversion linker and no Google tag on every page. Conversion tags fire, but they have no click to report, and Google Ads shows far fewer conversions than your CRM.
  2. The linker only on the homepage. Ads that point at service pages or landing pages lose the click.
  3. Redirects that drop the GCLID before the linker runs, for example an http to https redirect or a URL shortener that discards the query string. The linker can’t store what never reaches the page.
  4. A booking or checkout tool on another domain with no cross-domain linking. The lead happens, the click is lost.
  5. A custom cookie prefix on the linker that the conversion tags don’t know about.
  6. Blocking the linker with a consent trigger instead of relying on its built-in consent checks.

If conversions are still missing after all of this, my Google Ads conversion tracking not working checklist goes through the other causes.

FAQ

Do I still need the conversion linker if I use the Google tag?

Not if a Google tag for your Google Ads destination loads on every page; it stores the click information itself. In GTM I add the conversion linker anyway, because it guarantees the click is stored on every page.

First-party cookies named _gcl_*, such as _gcl_aw (Google Ads clicks) and _gcl_gs, on your top-level domain, plus a local storage entry called _gcl_ls.

Does the conversion linker work with GA4?

GA4 doesn’t need it. The conversion linker serves Google Ads and Floodlight tags. GA4 records the click through its own tag, and if you import GA4 key events into Google Ads, that path doesn’t use the linker’s cookies.

Which trigger should the conversion linker use?

All Pages, which is Google’s recommendation. Initialization – All Pages works too. Avoid limiting it to a list of landing pages.

Does the conversion linker work across subdomains?

Yes, by default. The cookies are set on the top-most domain, so subdomains share them. Cross-domain linking is only needed between different domains.

Need help with your conversion tracking?

The conversion linker is a small tag, but when it’s missing or misconfigured, Smart Bidding learns from a fraction of your real leads. I check the whole chain, from the ad click to the conversion in Google Ads. Let’s review your conversion tracking.

Daniel Timponi

Digital Marketing Analyst & Consultant · 17+ years crafting digital marketing that converts.

Schedule a call