GTM Conversion Linker: How to Set It Up and Why It Matters

The Google Tag Manager Conversion Linker is a built-in tag that stores ad-click identifiers in first-party cookies so Google's ad platforms can tie conversions back to the correct click. Without it, your Google Ads, Google Analytics 4, and Floodlight conversions can lose attribution, especially after browser cookie restrictions. Set it up once and it runs silently on every page.

What Is the GTM Conversion Linker?

The Conversion Linker is a tag template inside Google Tag Manager that detects when a user arrives from a Google ad click and writes the associated click identifier (such as the Google click ID, or gclid) into a first-party cookie on your own domain. Google's ad and analytics tags then read that cookie to connect a later conversion event with the original paid click.

It is not a tracking tag that sends data anywhere. It is a helper tag that formats and stores identifiers locally so the rest of your measurement stack can use them. You can read more about the core tool in our Google Tag Manager guide.

Why Does the Conversion Linker Matter for Tracking?

Attribution depends on linking a conversion to the click that caused it. When the Conversion Linker is missing or misconfigured, you get three concrete problems:

  • Under-reported conversions in Google Ads, because the platform cannot match the conversion to a known click.
  • Broken or incomplete GA4 attribution, since GA4 relies on the same first-party click identifiers for paid-source reporting.
  • Wasted ad spend, because Smart Bidding optimizes toward the conversions it can see, and invisible conversions distort the signal.

This matters most in a world of shrinking third-party cookies. First-party cookies set by the Conversion Linker are far more durable than cross-site identifiers, which makes the tag a foundational piece of resilient measurement.

How Does the Conversion Linker Work?

When a visitor clicks a Google ad, the landing-page URL contains a parameter such as ?gclid=... (for Search and Display) or ?gbraid=... / ?wbraid=... (for app and some Display campaigns). The Conversion Linker tag fires on that page, reads the parameter, and writes a first-party cookie scoped to your domain that holds the identifier and an expiry.

Later, when the same visitor converts, your Google Ads or GA4 tag reads the cookie and sends the identifier back to Google. The platform matches it to the original click. The whole exchange happens in the browser using your own domain, which is why it survives many cookie-restriction scenarios that break older approaches.

The stored identifier is not permanent. Google sets the cookie with an expiry that matches the click's attribution window, after which it refreshes on the next paid click. This is why a single Conversion Linker deployment keeps working across many campaigns without manual upkeep: every new click refreshes the relevant cookie automatically.

How to Set Up the Conversion Linker in Google Tag Manager

The setup takes about five minutes and rarely needs updating afterward. Follow these steps:

  1. Open your container in Google Tag Manager and go to Tags, then click New.
  2. Name the tag "Conversion Linker" and click Tag Configuration.
  3. Choose Conversion Linker from the tag types.
  4. Leave the default trigger as "All Pages" (the tag needs to fire on the first page a click lands on, which is almost always every page).
  5. Save and publish the container.

That is the entire setup. The tag has optional advanced settings, such as restricting it to specific cookie domains, but most sites should use the default configuration. If you are building out a broader server-side pipeline, pair this with our GA4 server-side tracking guide.

Conversion Linker vs Server-Side Tagging: What Is the Difference?

The Conversion Linker and server-side tagging solve different parts of the measurement problem, and you usually want both:

CapabilityConversion LinkerServer-Side Tagging
Stores ad click IDs in first-party cookiesYesNo (it routes tag requests instead)
Reduces data loss from cookie restrictionsYesYes
Sends events through your own serverNoYes
Setup effort5 minutesSignificant

In short, the Conversion Linker is the lightweight, always-on foundation; server-side tagging is the heavier upgrade that gives you control over the request path. Start with the Conversion Linker, then graduate to server-side when you need it.

Common Conversion Linker Mistakes to Avoid

  • Firing it only on a thank-you page instead of All Pages, which means it misses the landing page where the click ID first appears.
  • Setting the cookie domain incorrectly on a subdomain, which can prevent the identifier from being read later.
  • Assuming it sends conversion data, when it only stores identifiers for other tags to use.
  • Disabling it during a container cleanup because the name does not obviously say "tracking".

How Do I Verify the Conversion Linker Is Working?

Use Google Tag Manager Preview mode and the browser's developer tools to confirm the tag fires and the cookie is set:

  1. Open Tag Manager Preview, navigate to your site, and confirm the Conversion Linker tag appears under Tags Fired on the landing page.
  2. In your browser, open Developer Tools, go to the Application tab, and look under Cookies for your domain.
  3. You should see a cookie such as _gcl_aw or _gac with a value containing the click identifier shortly after a Google click lands.
  4. In GA4, compare a paid campaign's reported conversions before and after deployment; a sudden correction toward expected values indicates it is working.

If the cookie never appears, check that the tag triggers on All Pages and that no cookie-consent setting is blocking first-party writes. For deeper GA4 instrumentation, see our GA4 conversion tracking setup guide.

How Does the Conversion Linker Relate to Enhanced Conversions?

Enhanced Conversions and the Conversion Linker solve adjacent problems. The Conversion Linker preserves the ad click identifier in a first-party cookie. Enhanced Conversions improves the conversion signal itself by hashing and sending first-party customer data such as an email, so Google can reconstruct conversions that browser limits would otherwise drop. They are complementary: the Linker keeps the click side intact, and Enhanced Conversions keeps the conversion side intact. Most mature Google Ads accounts should run both, because together they cover the two most common points of attribution loss.

When Does Attribution Still Break Despite the Linker?

The Conversion Linker is necessary but not sufficient. Attribution can still fail when:

  • The user clears first-party cookies or uses a browser with aggressive tracking prevention between click and conversion.
  • The conversion happens outside the cookie lifetime, which is typically up to 90 days for Google click cookies.
  • The landing page strips the gclid parameter before the tag fires, often because of a redirect or a custom router that drops query strings.
  • Consent settings block the cookie write on the first visit, and the user converts on a later session without re-consent.

When you see a gap between platform-reported and modeled conversions, walk this list before assuming the Linker is at fault. In most cases the fix is preserving the URL parameter through redirects or loosening the consent gate for necessary first-party identifiers. The Linker is the foundation, not the entire attribution strategy.

Key Takeaways

  • The Conversion Linker is a five-minute, set-once tag that preserves ad-click attribution.
  • It stores first-party cookies that survive many browser restrictions better than legacy methods.
  • It does not send data; it only prepares identifiers for Google Ads and GA4 tags.
  • Fire it on All Pages, not just conversion pages, or it will miss the initial click ID.
  • Pair it with server-side tagging when you need full control over the event path.

Frequently Asked Questions

Is the GTM Conversion Linker Required If I Already Use Google Ads Tags?

Yes. The Google Ads conversion tag can read the gclid from the URL directly in simple cases, but the Conversion Linker is what stores it in a durable first-party cookie for return visits, cross-page journeys, and post-cookie-restriction resilience. Google recommends it as a baseline for all sites running Google Ads.

Does the Conversion Linker Affect Page Performance?

No. It is one of the lightest tags in GTM. It performs a small amount of cookie-writing logic on page load and then stops. You will not measurably change load time by adding it.

Will the Conversion Linker Work with Consent Management Platforms?

It can, but behavior depends on your consent configuration. If you block all cookies before consent, the tag may be unable to write its first-party cookie until the user accepts. Configure your consent triggers so the Conversion Linker is allowed to set strictly necessary first-party identifiers, or fire it after consent for analytics.

Do I Need a Separate Conversion Linker for Google Ads and GA4?

No. A single Conversion Linker tag covers both. It writes the shared click identifiers that every Google tag on the page can read, so one instance on All Pages serves Google Ads, GA4, and Floodlight.

What Happens If I Delete the Conversion Linker Tag?

You will not lose historical data, but future conversions from returning visitors and cookie-restricted browsers will gradually lose attribution back to the click. This shows up as lower reported Google Ads conversions and weaker Smart Bidding signals, often weeks after removal.