Google Ads conversion tracking breaks across different domains because browser cookies are domain-specific. When a user clicks an ad on Domain A and converts on Domain B, the GCLID (Google Click ID) parameter must be explicitly passed between domains. There are 3 methods to fix this: GA4 cross-domain measurement, Google Tag Manager configuration, and manual GCLID passing.
What Is Cross-Domain Conversion Tracking in Google Ads?
Google Help explains the official process in Set up conversion tracking for your website.
Cross-domain conversion tracking is a setup that allows Google Ads to record a conversion occurring on a different domain from the one the user landed on after clicking an ad.
Examples include:
Gemini SEO Visibility 2026: 4 Ranking Shifts and How to Reclaim Organic Traffic
How to Demote Sitelinks: What Replaced the Tool and 4 Current Methods
- A user clicks an ad landing on shop.example.com but completes a purchase on checkout.paymentprovider.com.
- A user visits example.com from an ad but fills out a lead form on forms.thirdparty.com.
- A user browses brand.com from an ad but books an appointment on booking.anotherdomain.com.
The GCLID parameter identifies the original ad click. If this parameter is not passed to the second domain, Google Ads cannot attribute the conversion to the correct campaign.
Why Does Conversion Tracking Break Across Different Domains?
Conversion tracking breaks across different domains because browser cookies are scoped to a single domain. The GCLID stored in a cookie on Domain A is not accessible to Domain B. When the user moves from Domain A to Domain B without carrying the GCLID in the URL, Google Ads loses the connection to the original ad click.
According to Google Ads Help documentation, auto-tagging appends the GCLID as a URL parameter to the landing page URL. If this parameter is not forwarded to the conversion domain, the conversion is recorded as unattributed.
What Is a GCLID and Why Is It Required for Cross-Domain Tracking?
A GCLID (Google Click Identifier) is a unique alphanumeric string appended to the landing page URL by Google Ads auto-tagging. It identifies the specific ad click that brought the user to the site. Cross-domain conversion tracking requires the GCLID to be present in the URL of the conversion page on the second domain.
How Do You Set Up Google Ads Conversion Tracking Across Different Domains?
Setting up cross-domain conversion tracking requires 1 of 3 methods depending on the technical setup of both domains.
Method 1: How Do You Use GA4 Cross-Domain Measurement Linked to Google Ads?
GA4 cross-domain measurement automatically passes the GCLID and session data between domains using the _gl URL parameter. Setting it up requires 5 steps:
- Open Google Analytics 4 and navigate to Admin > Data Streams > Web > Configure Tag Settings.
- Select "Configure your domains" under the cross-domain measurement section.
- Add both domains (e.g., example.com and paymentprovider.com) to the domain list.
- Link the GA4 property to Google Ads under Admin > Google Ads Links.
- Import GA4 conversion events into Google Ads under Tools > Conversions > Import > Google Analytics 4.
Once linked, GA4 passes session and click data across domains automatically. Google Ads attributes the conversion to the original ad click without additional developer work.
Method 2: How Do You Configure Google Tag Manager for Cross-Domain Conversion Tracking?
Google Tag Manager uses a Conversion Linker tag to capture and store the GCLID across domains. Setting it up requires 4 steps:
- Open Google Tag Manager and create a new tag. Select "Conversion Linker" as the tag type.
- Enable the "Enable linking on all pages" option within the Conversion Linker settings.
- Add the domain receiving the conversion (Domain B) as an "Auto Link Domain."
- Publish the container and verify the GCLID is appended to outgoing links using Google Tag Assistant.
The Conversion Linker tag must be installed on both domains. It reads the GCLID from the URL on Domain A and rewrites outbound links to include the GCLID before the user navigates to Domain B.
Method 3: How Do You Pass the GCLID Manually Between Domains?
Passing the GCLID manually requires developers to extract the GCLID from the landing page URL and append it to all outbound links pointing to the conversion domain. The process involves 3 steps:
- Read the GCLID value from the URL parameter using JavaScript:
const gclid = new URLSearchParams(window.location.search).get('gclid'); - Append the GCLID to all outbound links pointing to the conversion domain:
conversionPageURL + '?gclid=' + gclid - On the conversion domain, configure the Google Ads conversion tag to read the GCLID from the URL parameter instead of a first-party cookie.
Manual GCLID passing is used when Google Tag Manager is not available on 1 or both domains.
How Do You Verify Cross-Domain Conversion Tracking Is Working?
Verifying cross-domain conversion tracking requires 3 checks:
- Click a Google Ad and land on Domain A. Inspect the URL to confirm the GCLID parameter is present (e.g., ?gclid=TeSter-ABC123XYZ).
- Click a link that navigates to Domain B. Inspect the new URL to confirm the GCLID or _gl parameter is still appended to the URL.
- Complete the conversion action on Domain B. Check Google Ads under Tools > Conversions within 24 hours to confirm the conversion is recorded and attributed.
What Tool Confirms the GCLID Is Passing Between Domains?
Google Tag Assistant (available as a Chrome browser extension) confirms the GCLID is passing between domains. It displays active tags, the GCLID value detected in the URL, and whether the Conversion Linker tag is firing correctly on each domain.
What Are the 4 Most Common Cross-Domain Conversion Tracking Errors?
The 4 most common errors in cross-domain conversion tracking are listed below:
| Error | Cause | Fix |
|---|---|---|
| GCLID missing from Domain B URL | Conversion Linker not installed on Domain A | Add Conversion Linker tag to Domain A in GTM |
| Conversions recorded as direct traffic | Auto-tagging disabled in Google Ads | Enable auto-tagging under Google Ads > Settings > Account Settings |
| _gl parameter stripped by Domain B | Domain B server removes unknown URL parameters | Contact Domain B administrator to whitelist _gl and gclid parameters |
| GA4 not passing data to Google Ads | GA4 property not linked to Google Ads account | Link GA4 to Google Ads under GA4 Admin > Google Ads Links |
Does Cross-Domain Conversion Tracking Work With Consent Mode?
Yes, but with limitations. Google Ads Consent Mode v2 is required for cross-domain tracking to function correctly in regions governed by GDPR and similar privacy regulations. Examples include the European Union, United Kingdom, and Switzerland.
Consent Mode v2 introduces 2 parameters that directly affect cross-domain tracking:
- ad_storage: Controls whether the GCLID cookie is written to the user's browser.
- ad_user_data: Controls whether user data is sent to Google for conversion modelling.
When a user denies consent on Domain A, the GCLID cookie is not stored. Google Ads uses modelled conversions to estimate attribution for that user. When a user grants consent, the GCLID passes normally between domains and conversion tracking is fully accurate.
Implementing Consent Mode v2 alongside cross-domain tracking requires both domains to initialize the Google Consent Mode code before any Google tags load on the page.
Waleed Qamar holds a BSc in Computer Science from Purdue University and has spent the years since turning that technical foundation into something the curriculum never covered: figuring out why websites rank, why they fall, and why most businesses never find out until it is too late.
Pakistan-born and based between the United States and South Asia, he has managed search visibility for e-commerce stores, local service businesses, and SaaS startups across two continents. He started in SEO when guest posting still worked, survived the Penguin update, and has rebuilt client sites from scratch after algorithm hits more than once.
He has watched good businesses get sold packages that looked like progress and delivered nothing lasting. He has also seen the right approach quietly double a site’s traffic without a single press release about it.
His writing on SEO By Highsoftware99 covers Google algorithm updates, autocomplete optimization, semantic SEO structure, and the widening gap between what agencies promise and what Google actually rewards in 2026.
He knows what a traffic cliff looks like in Search Console on the morning you discover it.