How the Conversion Linker works
When someone clicks a Google ad, an identifier is added to the landing page URL. That identifier lives in the address bar of the first page only. If the visitor browses to a second page, fills in a form and lands on a thank-you page, the identifier has long gone from the URL, and the conversion tag on that page has nothing to connect the sale back to the click.
The Conversion Linker tag solves that. It runs on every page, reads any Google click identifier present in the URL, and writes it into a first-party cookie on your own domain. Conversion tags that fire later read the cookie instead of the address bar. In Google Tag Manager it is a built-in tag type with almost nothing to configure: you set it to fire on all pages and leave it alone.
Why the Conversion Linker matters
Without it, only conversions that happen on the landing page itself can be attributed reliably, and almost no real business converts that way. The visible symptom is a Google Ads account reporting far fewer conversions than the CRM or the inbox suggests, with the shortfall concentrated in journeys that take more than one page.
It matters more on browsers that restrict how long scripts can keep cookies, because a first-party cookie written by your own site is treated more kindly than one written by a third party. It also matters for anything that later depends on the identifier — offline conversion uploads and enhanced conversions both need the click reference to have survived the journey.
Common mistakes with the Conversion Linker
Firing it only on the thank-you page is the classic error, and it is exactly backwards: by then the identifier is gone. It must fire on the page the visitor arrives at, which means all pages, because any page can be a landing page.
The second problem is tag order. If the conversion tag fires before the linker has written its cookie on a single-page journey, the reference is missed. The third is a site spread across domains — a booking engine or payment page on another domain will not see a cookie set on the main site unless cross-domain settings are configured, and the linker alone does not fix that.
How to get it right
Create one Conversion Linker tag, set the trigger to all pages, and make sure nothing blocks it before the page renders. Then test the full journey: click a live ad or paste a URL carrying a Google click identifier, move through two or three pages, complete the form, and confirm the conversion registers against the ad rather than as direct traffic.
If the site uses a consent banner, decide deliberately what happens before consent is given, and test both states rather than assuming. And if measurement spans several domains, list them in the linker’s cross-domain settings and re-test the handover. Most of this sits naturally inside a wider tag management setup rather than being a one-off fix.
