Google Tag Manager Conversion Linker: Complete Setup Guide
5 min read
The conversion linker takes four minutes to configure. Every guide on the internet tells you this. They are not wrong. The problem is what they skip over after you publish it.
Simul Sarker
Founder & Product Designer of DataCops
Last Updated
June 2, 2026
GTM Conversion Linker: Complete Setup Guide (And the Part Nobody Documents)
Between 20 and 40 percent of the humans you are paying Google to send you will never fire that tag. Not because you misconfigured it. Not because you forgot the All Pages trigger. Because the GTM container it lives inside is blocked before it ever loads, and the attribution for those visitors vanishes silently, without a single error in your dashboard. Your conversion data looks complete. It is not.
That is the honest version of this guide. You will get the mechanics. You will also get the part the official documentation and the vendor tutorials leave out.
What the Conversion Linker Actually Does
When someone clicks your Google Ad, Google appends a GCLID parameter to the destination URL. That string looks like this: ?gclid=CjwKCAiA.... It contains the click data Google needs to match the visit to the conversion. Without it, the conversion fires on Google's end with no attribution. The click becomes a ghost.
The conversion linker tag reads that GCLID from the URL on landing, then stores it in a first-party cookie on your domain. The _gcl_aw cookie. When the conversion fires later, on a thank-you page or after a form submit, the Google Ads conversion tag reads back the stored GCLID and sends it along with the event. Google matches the conversion to the click. Attribution works.
That is the whole mechanism. The linker is a bookkeeping step, not a tracking layer. It does one job: preserve the click ID between landing and conversion so the attribution math can run.
The official docs call it essential. They are right. They do not tell you how many sessions it is already failing on.
The Setup (Clean and Complete)
Step 1: Go to Tags in your GTM web container
Log into your Google Tag Manager account. Select the web container for the property you are tracking. In the left sidebar, click Tags, then New.
Step 2: Select Conversion Linker as the tag type
Click Tag Configuration. Scroll through the built-in tag types and select Conversion Linker. You will see two options: Enable linking across domains and Use URL redirect. Leave both off for a standard single-domain setup. If you run separate domains for landing pages and conversion pages, enable cross-domain linking and add the relevant domains. If you use URL redirects before the final landing page loads, enable the redirect option.
Step 3: Set the trigger to All Pages
Click Triggering. Select the All Pages trigger. This is not optional. The linker needs to fire on every page that could be a landing page for an ad click. If you restrict it to a specific URL, you will miss every campaign that sends traffic to a homepage, a collection page, a blog post, or any other entry point that is not your exact thank-you page. Use All Pages. Fire it early.
Step 4: Name it and save
Name it something unambiguous. "Conversion Linker - All Pages" works. Save the tag.
Step 5: Verify in Preview mode before publishing
Click Preview in the top right corner of GTM. Enter the URL of a page you expect ad traffic to land on. You are checking two things. First: does the Conversion Linker tag appear in the tag summary for the page view event? Second: does it fire in the Succeeded column, not the Paused or Not Fired column?
Open your browser's developer tools. Go to Application, then Cookies. Filter for _gcl. After the linker fires on a URL containing a GCLID parameter, you should see _gcl_aw with a value. That cookie is your confirmation the linker ran and stored the click data.
Step 6: Publish
Click Submit. Add a version description. Publish.
You are done with the mechanics. Four minutes, as advertised. Now for what the guide does not tell you.
Why It Fails Silently for 20 to 40 Percent of Your Paid Traffic
The GTM container is a JavaScript file hosted on googletagmanager.com. That domain is on every major ad blocker's filter list. uBlock Origin, the most widely used browser extension in the world, blocks it by default. Brave browser's shields block it. Pi-hole blocks it at the DNS level. Firefox has started blocking it via Enhanced Tracking Protection.
When the container does not load, nothing inside it runs. The conversion linker is inside it. So for a user running uBlock Origin, your perfectly configured tag does not fire. The GCLID in their landing page URL expires. The _gcl_aw cookie is never written. When they convert, that conversion reaches Google with no GCLID attached. It becomes an unattributed conversion. Your ROAS on that campaign is understated. Your Smart Bidding trains on an incomplete signal.
The users who block ad trackers are, disproportionately, the people you most want to track accurately. Privacy-conscious buyers. Technical audiences. High-income demographics. They are not average. They skew toward the segments where ad CPCs are highest. You are paying the most for those clicks and measuring the fewest of their conversions.
ITP compounds this separately. Safari's Intelligent Tracking Prevention caps the lifetime of script-set first-party cookies, often to seven days, sometimes to 24 hours for link-decorated traffic. The _gcl_aw cookie the linker writes is a script-set cookie. On Safari, it can expire well inside a normal consideration window. A user clicks your ad on Monday. The cookie expires Wednesday. They convert Thursday. Attribution fails, not because the linker did not fire, but because the linker's output did not survive long enough to be useful.
<function_calls> <invoke name="web_fetch"> <parameter name="url">https://joindatacops.com/resources/google-tag-manager-conversion-linker-complete-setup-guide/