Google Tag Manager Conversion Linker: Complete Setup Guide

Google Tag Manager's Conversion Linker tag is not glamorous. It doesn't fire pixels, doesn't send events to Meta, and won't show up in your GA4 reports. What it does is preserve the click ID that Google uses to credit your ads for conversions, and when it's missing or misconfigured, every downstream conversion you track becomes unreliable. In 2026, with Google Tag Gateway now offering free server-side Google CAPI and Consent Mode v2 enforcement actively being audited, getting this foundation right matters more than it ever has.

Most guides treat the Conversion Linker as a checkbox. Install it, move on. That framing misses the real problem: the tag interacts with browser storage, cookie lifetimes, ITP restrictions on Safari, and your tag firing order in ways that aren't obvious from the GTM UI. This guide covers how it actually works, where it silently fails, and what you need to do differently in a first-party tracking setup versus a standard pixel-only deployment.

This includes situations where the Conversion Linker alone isn't enough, where a server-side layer changes everything, and where DataCops is not the right call.

Quick Answers

What does the Conversion Linker tag do in GTM? The Conversion Linker reads the GCLID (Google Click Identifier) from the URL when a user arrives from a Google Ads click, then stores it in a first-party cookie on your domain. Without this, the Google Ads conversion tag can't match pageview events to the original click. It also supports GBRAID and WBRAID parameters used for iOS app and web attribution since SKAdNetwork changes.

Does every GTM setup need a Conversion Linker? Yes, if you're tracking any Google Ads conversions via GTM. The exception is if you're using the Google Site Tag (gtag.js) directly outside of GTM, since that script handles linker functionality natively. If you're using GTM and relying on any Google Ads conversion tag, the Conversion Linker is required.

Where should the Conversion Linker fire? On all pages, triggered by "All Pages," and critically it must fire before your Google Ads conversion tags. If your conversion tag fires first and the GCLID hasn't been stored yet, that conversion is unattributable. GTM fires tags in order of priority, and the Conversion Linker should have a higher priority number or a dedicated sequencing setup.

What's the difference between "Linker cookie" and "auto-tagging"? Auto-tagging in Google Ads appends the GCLID to your destination URL. That's a Google Ads account setting. The Conversion Linker is the GTM mechanism that reads and stores that GCLID. Both must be active. Turning off auto-tagging means there's no GCLID to read. Having auto-tagging without the Conversion Linker means the GCLID sits in the URL and gets lost on the next navigation.

How long does the GCLID cookie last? By default, the first-party cookie the Conversion Linker creates has a 90-day lifetime. That cookie survives browser restarts but is subject to ITP on Safari, where cookies set via JavaScript can be reduced to 7 days or eliminated entirely depending on the ITP version. This is where first-party server-set cookies become important for high-Safari-traffic audiences.

What happens when someone clicks a Google ad and lands on an HTTP page? If your site isn't fully HTTPS, the GCLID cookie may not be set correctly due to Secure attribute requirements. Any redirect from HTTP to HTTPS before the Conversion Linker fires will strip the GCLID from the URL, and attribution is lost. This is especially common with legacy redirect chains.

Does the Conversion Linker work with cross-domain tracking? Yes, but you need to configure it explicitly. In the Conversion Linker settings, enable "Link Domain" and specify the domains you want to pass the GCLID across. If a user clicks your ad, lands on domain A, and then converts on domain B, the GCLID must be decorated onto links between those domains. Otherwise, Google sees domain B as a new unattributed session.

What changed with server-side GTM and the Conversion Linker? With server-side GTM (sGTM), the Google Ads conversion tag runs in a server container rather than the browser. The Conversion Linker still runs client-side to capture and store the GCLID, but the conversion event and the GCLID are sent from your server to Google's API instead of from the browser. This improves reliability and partially bypasses ad blockers, but the client-side Conversion Linker remains necessary for initial GCLID capture.

How the Conversion Linker Actually Works

When someone clicks a Google Ads link, Google appends a parameter to the URL that looks like gclid=CjwKCAjw.... This is a unique identifier tied to that specific click, that ad, that keyword, and that auction. Without it, Google can't know which ad impression led to a conversion.

The Conversion Linker tag reads this parameter from the URL on landing, then writes it to a first-party cookie under your domain. From that point forward, whenever your Google Ads conversion tag fires (on a purchase confirmation page, a form submission, a phone call, wherever you've set it up), it reads the stored GCLID and sends it back to Google alongside the conversion event. Google can then close the attribution loop.

The key word is "first-party." The cookie is set on your domain, not Google's. That's why ad blockers that block third-party Google scripts don't necessarily break the Conversion Linker, assuming the linker tag itself has already fired. However, if your GTM container is being blocked before the Conversion Linker fires, the cookie never gets set in the first place. This is the gap that server-side tracking addresses.

Setting Up the Conversion Linker in GTM: Step by Step

Open your GTM web container. Navigate to Tags, then New. Choose tag type and search for "Conversion Linker." The tag is built into GTM natively, no template needed.

The configuration options are minimal by design. You'll see:

Enable linking across domains. Leave this off if you're tracking a single domain. Enable it if you have subdomains that should share attribution data (for example, shop.yourdomain.com and www.yourdomain.com as separate origins), or if you're passing users between distinct domains before conversion.

Override cookie settings. The default cookie period is 90 days, scoped to your domain. You can change this here if your business requires shorter data retention. Do not extend it past 90 days for most use cases, as Google's attribution model doesn't use GCLID data beyond that window in most scenarios.

For the trigger, set this to "All Pages" (the built-in trigger). This ensures the GCLID is captured regardless of which page a user lands on, which matters for direct-to-cart links, landing page variants, and any non-homepage entry points.

Tag sequencing: in your Google Ads conversion tags, go to "Advanced Settings" and set up tag sequencing to fire the Conversion Linker before each conversion tag. Alternatively, set the Conversion Linker's tag priority to a value higher than your conversion tags (GTM fires higher priority tags first within the same trigger firing).

Publish the container. Verify by clicking a Google Ads link (or simulating one by appending ?gclid=test123 to your URL), opening browser developer tools, going to Application, then Cookies, and checking for a cookie named _gcl_aw on your domain. If it's there, the Conversion Linker is working.

Where the Conversion Linker Silently Fails

Safari ITP. Intelligent Tracking Prevention on Safari aggressively limits the lifetime of cookies set by JavaScript. If your Conversion Linker cookie is set via client-side JavaScript (which it is by default), Safari may cap it at 7 days or prevent it from persisting across sessions entirely. For businesses with significant iOS or Mac traffic, this is a meaningful attribution gap. The fix is server-side cookie setting, which requires either server-side GTM or a first-party proxy setup.

Page speed and tag load order. If the user's browser loads your page and then navigates away before GTM fully initializes, the Conversion Linker never fires. This is rare but happens on very fast navigators (users who click the back button immediately) and on pages with heavy JavaScript that blocks GTM initialization. GTM's performance impact is worth auditing if you suspect this. See the advanced conversion tracking implementation guide for load-order diagnostics.

Redirect chains stripping GCLID. If your ads point to a URL that redirects before the user's browser loads your GTM container, the GCLID in the original URL may be lost. Common culprits: URL shorteners, affiliate redirect systems, old HTTP-to-HTTPS redirects, and regional redirect scripts. The GCLID must survive all redirects and be present in the final URL that loads your GTM container.

Ad blockers blocking GTM itself. The Conversion Linker can only work if GTM loads. Ad blockers such as uBlock Origin and Brave Shields block googletagmanager.com by default. According to Bounteous research, approximately 80% of server-side GTM setups are detectable and blockable by browser extensions. If a user with an ad blocker clicks your Google ad, lands on your site, and GTM is blocked, the Conversion Linker never fires and the GCLID is lost. This is where first-party script serving matters: running your GTM container from your own subdomain (such as tracking.yourdomain.com) bypasses most ad blocker rules targeting googletagmanager.com. The complete history of third-party cookies explains why this architecture matters.

Cross-domain gaps. If you enable cross-domain tracking in the Conversion Linker but forget to add a domain to the list, GCLID decoration won't happen on links to that domain. Users who convert on an unlisted domain appear as unattributed. Audit your cross-domain config any time you add a new subdomain or brand domain to your funnel.

Missing auto-tagging on the Google Ads side. The Conversion Linker can only read a GCLID that exists. If auto-tagging is disabled in your Google Ads account settings, there's no GCLID in the URL to capture. This happens most often when someone manually sets UTM parameters in their ad URLs and disables auto-tagging to prevent parameter conflicts. The fix is to either re-enable auto-tagging or use Google's parallel tracking with manual parameters.

The Conversion Linker in a Server-Side Setup

Standard client-side GTM with a Conversion Linker covers the basics. But in a server-side setup, whether via raw server-side GTM or a managed platform, the architecture changes.

In client-side only GTM, the browser does everything: reads the GCLID from the URL, stores the cookie, fires the conversion tag, sends the hit to Google. Every step happens in the user's browser, which means every step is subject to browser limitations, ad blockers, and cookie restrictions.

In a server-side setup, the GCLID capture still happens client-side (the Conversion Linker tag still runs in the browser to read the URL parameter), but the conversion event itself is sent from your server to Google's Measurement Protocol or Ads API. The server-to-server call isn't subject to browser-based blocking. The GCLID is passed as a parameter in that server call.

For WooCommerce setups specifically, the WooCommerce conversion tracking guide covers how to pass the GCLID through order metadata so it's available on the server at conversion time.

With Google Tag Gateway (launched January 2026), Google now offers a free path to first-party server-side deployment via Google Cloud Platform, Cloudflare, or Akamai. This reduces the infrastructure cost of server-side GTM to near zero for Google-only tracking. The tradeoff is that it's Google-only: it doesn't help with Meta CAPI, TikTok, or LinkedIn events.

Enhanced Conversions and the Conversion Linker: How They Interact

Enhanced Conversions (EC) is Google's mechanism for matching hashed first-party data (email, phone, name, address) to Google accounts to improve attribution when GCLID-based matching fails. This happens when users clear cookies, browse in incognito, or convert on a different device than they clicked on.

The Conversion Linker and Enhanced Conversions work in parallel, not in sequence. The Conversion Linker handles GCLID-based attribution. Enhanced Conversions handles identity-based matching as a fallback. You need both. A setup with only the Conversion Linker misses cross-device conversions. A setup with only Enhanced Conversions misses direct GCLID attribution.

For the Enhanced Conversions setup in GTM, you configure your Google Ads conversion tag to capture hashed user-provided data from your confirmation pages. This requires accessing form field values via GTM variables, hashing them (GTM can do this natively since 2023 with SHA-256 support), and passing them in the conversion tag. The Google Consent Mode v2 implementation guide covers how consent mode interacts with this flow, which is increasingly important given the June 15, 2026 Consent Mode v2 deadline for EEA advertisers.

Consent Mode v2 and What It Changes

If you're running Google Ads and collecting conversions from users in the EEA, Consent Mode v2 is not optional after June 15, 2026. It changes how the Conversion Linker behaves.

When a user rejects analytics or advertising consent, Consent Mode v2 instructs Google tags to operate in a restricted mode. Specifically, the ad_storage consent type controls whether the Conversion Linker can set and read cookies. If ad_storage is "denied," the Conversion Linker won't store the GCLID cookie. Instead, Google uses cookieless pings and modeled conversions to partially fill the attribution gap.

This means the Conversion Linker's effectiveness is directly tied to your consent acceptance rate. If 60% of your EEA users reject consent, 60% of your Google Ads conversions for those users become modeled rather than measured. Google's modeling has improved, but modeled conversions and measured conversions are not equivalent from a bidding signal standpoint.

The practical implication: if you're in EEA markets, the consent solution you choose directly impacts your Google Ads performance. A CMP that reduces friction in the consent flow (without violating GDPR) will increase your measured conversion rate. Most advertisers treat consent management as a compliance checkbox. It's actually an ad performance lever.

Debugging the Conversion Linker

The fastest way to verify the Conversion Linker is working is to use GTM's Preview mode alongside your browser's developer tools.

In GTM Preview, load any page on your site with ?gclid=test123 appended to the URL (you can use any string as the value for testing). You should see the Conversion Linker tag fire on the "All Pages" trigger before any conversion tags fire. In your browser developer tools under Application, then Cookies, you should see _gcl_aw set on your domain with the test GCLID value.

If the cookie isn't there, check: (1) the Conversion Linker tag trigger is set to All Pages, (2) the tag is published not just in preview, (3) your browser doesn't have extensions blocking GTM from loading, (4) you're not on a page with a CSP policy blocking external scripts.

For production verification, use Google Ads' "Tag Diagnostics" tool in your Ads account (Tools, then Measurement, then Tag Diagnostics). It will show you whether conversions are being received with valid GCLID data, whether Enhanced Conversions data is arriving, and whether there are any detected configuration errors.

Google Tag Assistant (the Chrome extension) can also validate that the Conversion Linker is firing and that GCLID data is being captured. Use it alongside GTM Preview for comprehensive validation. The testing and debugging conversion API events guide covers a broader debugging framework that applies to server-side setups as well.

The GCLID Problem That Server-Side Doesn't Fully Solve

Here's the part that most GTM guides skip: even with server-side GTM and a first-party Conversion Linker setup, you're still sending every conversion event to Google regardless of whether the converting user was a real human.

Bot traffic hitting your landing pages from Google Ads clicks generates GCLIDs. Those GCLIDs can get stored in cookies (or in your database if you're persisting them server-side). If a bot completes a form or fires a conversion event, that event gets sent to Google with a valid GCLID. Google counts it as a conversion. Your bidding algorithm learns from it.

Global invalid traffic averages 20.64% according to Fraudlogix 2026 data. For finance and legal verticals, the figure reaches 42%. Even at the lower end, if 15% of your Google Ads clicks are non-human, 15% of your "conversions" are teaching your bidding model the wrong patterns.

The Conversion Linker doesn't filter anything. It reads, stores, and passes the GCLID. What you do with it from there, and specifically whether you validate that the session was real before firing your conversion event, is entirely up to your implementation.

Platforms like DataCops address this at the infrastructure level by running each session through a 361B+ IP database that filters bots before any conversion events reach Google or Meta. The DataCops fraud traffic validation layer sits upstream of the conversion call, so bot sessions are excluded before CAPI fires. This doesn't replace the Conversion Linker; it works alongside it. The Conversion Linker still captures the GCLID from valid sessions, and the bot filter prevents invalid sessions from contributing conversion events.

For advertisers spending significant amounts on Google Ads, the question is whether the 15-42% of bot traffic touching your landing pages is a problem worth addressing at the conversion event level. If you're seeing inflated conversion counts, unexplained ROAS swings, or bidding algorithms that seem to be over-targeting low-quality segments, bot-polluted conversion data is a plausible contributor.

When NOT to Use DataCops

DataCops is the right call for multi-platform server-side conversion tracking with bot filtering. It's not the right call in several common scenarios.

If you only need Google CAPI and your traffic is entirely from non-bot-heavy sources, Google Tag Gateway (free since January 2026) gives you a first-party server-side Google tracking setup at zero cost. Setting it up takes under an hour on Google Cloud Platform or Cloudflare. There's no reason to pay for a managed platform when the free native option covers your use case.

If you're an in-house team with strong GTM expertise and want full control over your tag container and server infrastructure, Stape is the right move. At $17/month for Pro, it's the cheapest sGTM hosting available, with 80+ templates and full container access. DataCops is an outcome platform, not an infrastructure platform. If you want to own the infrastructure layer, Stape is built for that.

If you're a Shopify-only store doing $500K or more in monthly GMV where order-level tracking fidelity is the top priority, Elevar's deep Shopify-native integration may be worth the $200 to $950 per month premium. Elevar has order-level reconciliation that DataCops doesn't replicate at the same depth for Shopify-specific order flows.

If you need SOC 2 Type II certification today for enterprise compliance requirements, DataCops is in progress on this certification but doesn't have it completed. Datahash and some larger players have Type II in place. Don't let a sales process convince you that "in progress" is equivalent to "certified."

If your entire tracking requirement is Meta-only and you're a small operation with clean traffic, Meta's free 1-click CAPI (launched April 2026) may be all you need. It's native, zero-cost, and handles the basics. You give up bot filtering, multi-platform, and EMQ optimization, but if Meta is your only channel and your traffic quality is not a concern, it's a reasonable starting point.

Feature Comparison: Conversion Linker Ecosystem Options

Putting It Together

The Conversion Linker is a prerequisite, not a solution. It handles the mechanical work of capturing and storing GCLIDs so your Google Ads conversion tags can attribute properly. Getting it right means understanding tag firing order, cross-domain configuration, ITP limitations, and how it interacts with Consent Mode v2.

Once the Conversion Linker is working correctly, you're at baseline. You're tracking real conversions from non-blocked sessions with proper GCLID attribution. That's the floor. The ceiling is a setup where server-side conversion calls bypass ad blockers, bot sessions are filtered before they generate conversion events, and your bidding algorithms are learning from human behavior instead of synthetic traffic.

For teams running multi-platform campaigns across Google, Meta, TikTok, and LinkedIn, see the DataCops conversion API overview for how a unified server-side stack interacts with the client-side Conversion Linker foundation you've built.

For Shopify-specific setups, the Shopify conversion tracking tools guide covers how the Conversion Linker fits into a platform-specific implementation alongside order-level tracking.

The conversions you sent Google last month: how many can you prove came from sessions where a human clicked your ad, landed on your page, and completed a real action? If you're relying only on the Conversion Linker and a pixel, that answer is probably less certain than your conversion reports suggest.