Digital MicroEnterprise
Book a Call

The Complete Guide to Google Ads Cross-Domain Tracking

Leave a Comment / Measurement / By /

Updated: 2025-10-24

Master the art of accurate attribution across multiple domains and unlock your true Google Ads ROI

Picture this: A potential customer clicks your Google Ad, browses your main website, then completes their purchase on your secure checkout domain. Your Google Ads dashboard shows zero conversions from that campaign. Sound familiar?

You’re not alone. Cross-domain tracking issues are silently draining ROI from countless Google Ads accounts, and most advertisers don’t even realise it’s happening.

Table of Contents

What is Cross-Domain Tracking (And Why It’s Make-or-Break for Your ROI)

Cross-domain tracking is the technical bridge that connects user journeys across multiple websites. Without it, Google’s tracking systems treat each domain as a separate session, losing the crucial connection between your ad clicks and conversions.

Here’s what happens without proper cross-domain tracking:

  • User clicks your Google Ad → Lands on yourbrand.com (Tracked correctly)
  • User navigates to checkout → Moves to secure-checkout.com (New session starts)
  • User completes purchase → Conversion attributed to “(direct)” or referral (Your ad gets zero credit)

The result? Your best-performing ads appear to be duds, while your actual duds might look like winners. It’s a measurement nightmare that makes data-driven optimisation nearly impossible.

Choosing Your Architecture

Before diving into implementation, you need to make a critical decision about your tag architecture. This choice will affect everything from setup complexity to troubleshooting ease.

Two Valid Approaches Exist

Approach 1: Separate Google Tags (My Recommendation)

  • One Google Tag for GA4 (G-XXXXXXX)
  • One Google Tag for Google Ads (AW-XXXXXXX)
  • Cross-domain configured independently on each

Approach 2: Consolidated Single Google Tag

  • One Google Tag with multiple destinations
  • Cross-domain configured once for all platforms

My Recommendation: Separate Tags

After troubleshooting cross-domain tracking issues across various implementations, I recommend separate tags for most situations. Here’s why:

Easier Troubleshooting

When something breaks (and in cross-domain tracking, something often breaks), separate tags make diagnosis dramatically faster. In GTM Preview Mode, you immediately see which platform has the issue:

  • “Google Tag – GA4” fires correctly
  • “Google Tag – Google Ads” fails

With a consolidated tag, you see “Google Tag” fires and must dig through destination routing, network requests, and shared configurations to figure out which platform is actually broken.

Independent Configuration

Different platforms often need different settings:

  • GA4 might send user-provided data for enhanced measurement
  • Google Ads might not (due to different privacy requirements)
  • Different consent mode behaviors
  • Different server-side migration timelines
  • Different testing requirements

Separate tags let you configure each platform independently without complex workarounds.

Separation of Concerns

Following software engineering principles:

  • Each tag has one clear responsibility
  • Changes to GA4 don’t affect Google Ads
  • Different teams can own different tags
  • Rollbacks affect only one platform
  • Testing happens in isolation

The Trade-off

You’ll configure cross-domain settings twice (once per tag). This is a 30-second copy-paste operation that buys you hours of saved troubleshooting time when issues arise.

When Consolidated Makes Sense

Consolidated tags work well for:

  • Extremely simple websites with identical settings needed for all platforms
  • Beginners implementing their first tracking (can refactor later)
  • Non-GTM implementations (hard-coded tags in website code)
  • Rapid prototypes or MVPs
  • Single-person operations with no team complexity

Decision Framework

Use Separate Tags if:

  • You need different settings for GA4 vs Google Ads
  • Multiple teams manage different platforms
  • You value clear troubleshooting
  • You’re implementing cross-domain tracking (complexity demands clarity)
  • You’re intermediate or advanced with GTM

Use Consolidated Tag if:

  • Absolute beginner overwhelmed by GTM concepts
  • Extremely simple website
  • Hard-coding tags without GTM
  • Identical configuration requirements for all platforms

Still not sure? Start with separate tags. It’s easier to consolidate later than to separate an existing consolidated setup.

Understanding Google Tags

Before we implement, let’s clarify Google’s tagging landscape because the naming is confusing.

The Google Tag Evolution

Google has fundamentally shifted from multiple product-specific tags to a unified “Google Tag” approach. What used to require separate tags for Google Ads, Analytics, and other products now works through a single tag type that can route data to multiple destinations.

Think of it as upgrading from multiple remote controls to one universal remote.

Understanding Tag IDs

You’ll encounter three types of IDs:

G-XXXXXXX (Google Analytics 4)

  • Used for GA4 measurement
  • Can also manage Google Ads data when Ads is added as a destination

AW-XXXXXXX (Google Ads – Legacy Format)

  • Used for Google Ads conversion tracking
  • Can also manage GA4 data when GA4 is added as a destination
  • Still widely used

GT-XXXXXXX (Google Ads – New Format)

  • Newer format for Google Ads accounts
  • Functionally identical to AW- IDs
  • If you see both GT- and AW- for the same account, they’re interchangeable

Key insight: A Google Tag can start with any of these IDs. The ID just indicates where the tag originated, not what platforms it can track. What matters is which destinations you configure, not the starting ID.

Why Google Tag Manager?

While you can implement Google Tags directly in your website code, Google Tag Manager (GTM) is strongly recommended because:

  • No code changes needed for tag updates
  • Built-in preview/debug mode
  • Version control and rollback capabilities
  • Easier team collaboration
  • Simpler testing before publishing

This guide covers both GTM and manual implementation, but GTM is the recommended approach.

Diagnosing Your Current Setup

If you already have tracking implemented, you need to understand your current setup before making changes.

Open Your GTM Container

Navigate to Google Tag Manager and open your workspace. Click “Tags” in the left menu.

Identify Your Current Setup

Look through your tags and identify which scenario matches your situation:

Setup A: Single Google Tag with Multiple Destinations

What you’ll see:

  • One tag called “Google Tag” (or similar)
  • When you open it, you see multiple destinations listed
  • For example: Primary ID is G-XXXXXXX with AW-XXXXXXX added as a destination

What this means:

  • You’re using the consolidated approach
  • One tag manages all platforms
  • Cross-domain settings apply to all destinations

Your migration path:

  • If you want to keep consolidated: Configure cross-domain settings (Section 6)
  • If you want separate tags: Follow migration instructions (Section 8)

Setup B: Separate Tags Already

What you’ll see:

  • A “Google Tag” with GA4 ID (G-XXXXXXX)
  • A “Conversion Linker” tag
  • Possibly separate “Google Ads Conversion Tracking” or “Google Ads Remarketing” tags

What this means:

  • You’re partially using the separate approach
  • GA4 has its own tag
  • Google Ads uses Conversion Linker for cross-domain functionality
  • This is functional but could be modernized

Your migration path:

  • You’re close to the recommended setup
  • Main improvement: Replace Conversion Linker with a proper Google Ads Google Tag
  • Follow refinement instructions (Section 8)

Setup C: Conversion Linker Only

What you’ll see:

  • “Conversion Linker” tag
  • “Google Ads Conversion Tracking” tags
  • “Google Ads Remarketing” tags (possibly)
  • NO “Google Tag” at all

What this means:

  • You’re using the legacy approach
  • Conversion Linker handles cross-domain parameter passing
  • No unified Google Tag exists yet
  • This still works but is outdated

Your migration path:

  • Full migration recommended
  • Create Google Tags for both GA4 and Google Ads
  • Follow full migration instructions (Section 8)

Setup D: Nothing Exists Yet

What you’ll see:

  • No Google Tags
  • No Conversion Linker
  • Starting from scratch

What this means:

  • You’re in the best position – no legacy configuration to untangle
  • Implement the recommended approach from scratch
  • Skip to implementation section (Section 5)

Where You Are vs Where You’re Going

Regardless of your current setup, here’s the recommended end state:

Recommended Final Configuration:

Google Tag Manager Container
  ├─ Google Tag (GA4)
  │   ├─ Tag ID: G-XXXXXXX
  │   ├─ Trigger: Initialization - All Pages
  │   └─ Cross-domain: domain1.com, domain2.com, domain3.com
  │
  └─ Google Tag (Google Ads)
      ├─ Tag ID: AW-XXXXXXX
      ├─ Trigger: Initialization - All Pages
      └─ Cross-domain: domain1.com, domain2.com, domain3.com

No Conversion Linker needed. No redundant tags. Just two Google Tags, each with one clear purpose.

Now let’s implement this.

This section covers the complete implementation of the recommended approach: separate Google Tags for GA4 and Google Ads.

Part A: Google Tag Manager Implementation

Step 1: Create Your GA4 Google Tag

1. Navigate to Tags

  • In your GTM workspace, click “Tags” in the left menu
  • Click the “New” button in the top right

2. Name Your Tag

  • Click “Untitled Tag” at the top
  • Name it: “Google Tag – GA4” (clear naming prevents confusion later)

3. Configure Tag Type

  • Click “Tag Configuration”
  • Select “Google Tag” from the tag type list

4. Enter Your GA4 Measurement ID

  • In the “Tag ID” field, enter your GA4 Measurement ID
  • This starts with G- followed by alphanumeric characters (e.g., G-ABC123XYZ)
  • Find this ID in GA4: Admin > Data Streams > Select your web stream > Measurement ID

5. Configure Cross-Domain Tracking

  • In the tag configuration, look for “Configuration Settings”
  • Click “Configure your domains” (may be under “More Settings” depending on your GTM version)
  • A panel will slide out from the right
  • Click “Add condition”
  • Leave the match type as “Contains”
  • Enter your first domain (e.g., yourbrand.com)
  • Do NOT include https:// or www. – just the domain name
  • Click “Add condition” again
  • Enter your second domain (e.g., secure-checkout.com)
  • Repeat for all domains in your user journey
  • Click “Save” to close the domain configuration panel

6. Set the Trigger

  • Click “Triggering” at the bottom of the tag configuration
  • Select “Initialization – All Pages”
  • This ensures the tag loads before other tags fire

7. Save the Tag

  • Click “Save” in the top right corner

Your GA4 tag is now configured.

Step 2: Create Your Google Ads Google Tag

1. Create a New Tag

  • In GTM, click “Tags” in the left menu
  • Click “New”

2. Name Your Tag

  • Name it: “Google Tag – Google Ads”

3. Configure Tag Type

  • Click “Tag Configuration”
  • Select “Google Tag”

4. Enter Your Google Ads ID

  • In the “Tag ID” field, enter your Google Ads conversion ID
  • This starts with AW- or GT- followed by numbers (e.g., AW-123456789 or GT-ABC-123)
  • Find this ID in Google Ads: Goals > Conversions > Summary > Click any conversion action > Tag setup > View tag setup instructions

5. Configure Cross-Domain Tracking

  • Click “Configure your domains”
  • Add the EXACT same domains you used for your GA4 tag
  • yourbrand.com
  • secure-checkout.com
  • Any other domains in your user journey
  • The domain lists must match between both tags
  • Click “Save”

6. Set the Trigger

  • Click “Triggering”
  • Select “Initialization – All Pages”

7. Save the Tag

  • Click “Save”

Your Google Ads tag is now configured.

Step 3: Handle Existing Conversion Linker (If Present)

If you have an existing Conversion Linker tag in your container:

Why You Should Pause It: When you have a Google Tag with an AW- or GT- ID firing on all pages, it includes Conversion Linker functionality built-in. A separate Conversion Linker tag becomes redundant and can cause conflicts.

How to Pause It:

  1. In GTM, go to your Tags list
  2. Find your “Conversion Linker” tag
  3. Click on it to open
  4. Click the three-dot menu in the top right
  5. Select “Pause”
  6. Save the tag

Exception: If you’re using Setup B (separate GA4 tag + Conversion Linker for Ads), and you DON’T want to create a separate Google Ads Google Tag, you can keep the Conversion Linker active. However, I recommend creating the Google Ads Google Tag for consistency and clearer troubleshooting.

Step 4: Preview and Test

Before publishing, use GTM’s preview mode to verify everything works:

1. Enter Preview Mode

  • Click “Preview” in the top right of your GTM workspace
  • Tag Assistant will open in a new tab

2. Connect Your Primary Domain

  • Enter your primary domain URL (e.g., https://yourbrand.com)
  • Click “Connect”
  • Your site opens with a “Connected” badge

3. Verify Tags Fire on Primary Domain

  • Look at the Tag Assistant panel
  • Find the “Container Loaded” event
  • Expand “Tags Fired”
  • Verify you see:
    • “Google Tag – GA4” (with a checkmark)
    • “Google Tag – Google Ads” (with a checkmark)
  • Both should show as successfully fired

4. Add Secondary Domain to Debugger

  • In Tag Assistant, click the X to close the debugger view
  • Check “Keep the domain enabled for debugging”
  • Click “Close debugger”
  • Click “Add domain”
  • Enter your secondary domain URL (e.g., https://secure-checkout.com)
  • Click “Connect”

5. Test Cross-Domain Navigation

  • Navigate from your primary domain to your secondary domain by clicking a link
  • Watch the Tag Assistant panel as you navigate
  • You should see events from both domains appearing

6. Verify URL Parameters

  • After navigating to the secondary domain, look at the URL in your browser
  • You MUST see a _gl parameter: https://secure-checkout.com/?_gl=1*abcde5*rs6h2f...
  • If this parameter is missing, cross-domain tracking is not working

7. Check for Errors

  • In Tag Assistant, look for any red error indicators
  • Expand any events that show errors
  • Address any issues before publishing

If everything looks good, proceed to publish.

Step 5: Publish Your Changes

1. Submit Container

  • Exit Preview Mode
  • Click “Submit” in the top right of GTM

2. Add Version Name and Description

  • Version Name: “Cross-Domain Tracking – Separate Tags Implementation”
  • Description: “Implemented separate Google Tags for GA4 (G-XXXXXXX) and Google Ads (AW-XXXXXXX) with cross-domain tracking configured”

3. Publish

  • Click “Publish” in the top right

Your changes are now live.

Step 6: Monitor After Publishing

After publishing, monitor both platforms for 48-72 hours:

In Google Analytics 4:

  • Check that pageviews are being recorded across both domains
  • Verify user journeys show continuity across domains
  • Look at User Explorer to see individual user paths

In Google Ads:

  • Check that conversions are being attributed correctly
  • Look for conversions from your campaigns (not all showing as “direct”)
  • Compare conversion volume before and after implementation

If you notice issues:

  • Re-enter Preview Mode and repeat the verification steps
  • Check the Troubleshooting section (Section 9) for common issues

Part B: Manual Implementation (Without GTM)

If you’re not using Google Tag Manager and are implementing tags directly in your website code, here’s how to set up cross-domain tracking.

Important: This approach requires editing your website’s HTML. If you’re not comfortable with code, consider implementing Google Tag Manager instead.

Step 1: Locate Your Current Tag Implementation

Your gtag.js code is typically in the <head> section of your website. You might have gotten this code from:

From Google Ads:

  • Navigate to Goals > Conversions > Summary
  • Select a conversion action
  • Click “Tag setup” tab
  • Choose “Install the tag yourself”

From Google Analytics 4:

  • Navigate to Admin > Data Streams
  • Select your web data stream
  • Click “View tag instructions”
  • Under “Install manually” tab, find the gtag.js snippet

Step 2: Implement Separate Tags with Cross-Domain Tracking

The key principle: Use separate gtag('config', ...) commands for each platform, with a single shared linker configuration.

The Complete Implementation:

html

<!-- Google tag (gtag.js) - Loads the library -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXX"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());

  // CROSS-DOMAIN TRACKING CONFIGURATION
  // This MUST come before any gtag('config', ...) commands
  gtag('set', 'linker', {
    'domains': ['yourbrand.com', 'secure-checkout.com', 'thank-you-page.com']
  });

  // Configure GA4
  gtag('config', 'G-XXXXXXX');

  // Configure Google Ads
  gtag('config', 'AW-XXXXXXX');
</script>

Critical Rules:

  1. Order Matters: The gtag('set', 'linker', ...) command MUST come before any gtag('config', ...) commands. If you place it after, the linker won’t work for the initial page load.
  2. Single Linker Configuration: You only need ONE gtag('set', 'linker', ...) command. It applies to all destinations automatically.
  3. Replace the IDs:
    • Replace G-XXXXXXX with your actual GA4 Measurement ID
    • Replace AW-XXXXXXX with your actual Google Ads Conversion ID
    • Replace the domain list with your actual domains
  4. Domain Format:
    • Do NOT include https:// or http://
    • Do NOT include www. unless you specifically need it
    • Just use the bare domain: example.com
  5. All Pages Need This Code: This exact snippet must be on EVERY page of ALL domains in your user journey.

Step 3: Verify the Implementation

Since you don’t have GTM Preview Mode, use these manual verification methods:

Test 1: Check for URL Parameters

  1. Clear your browser cache and cookies
  2. Visit your primary domain
  3. Click a link that takes you to your secondary domain
  4. Immediately check the URL in your browser address bar
  5. You MUST see a _gl parameter: https://secondary.com/?_gl=1*abc123*...
  6. If this parameter is missing, your cross-domain tracking is not working

Test 2: Verify Cookie Transfer

  1. Visit your primary domain with a test GCLID: https://yourbrand.com/?gclid=testGCLID12345
  2. Open Developer Tools (F12 or Right-click > Inspect)
  3. Go to the “Application” tab (Chrome/Edge) or “Storage” tab (Firefox)
  4. Expand “Cookies” in the left menu
  5. Select your primary domain
  6. Find the _gcl_aw cookie
  7. Note its value – it should contain your test GCLID: GCL.17099...testGCLID12345
  8. Now click a link to navigate to your secondary domain
  9. Open Developer Tools again
  10. Navigate to Cookies > Select secondary domain
  11. Verify the _gcl_aw cookie exists with the EXACT same value

If the cookie transfers with identical values: Your cross-domain tracking is working.

If the cookie doesn’t exist on the secondary domain: Your setup needs fixing.

Test 3: Check for JavaScript Errors

  1. Open Developer Tools (F12)
  2. Go to the “Console” tab
  3. Look for any red error messages related to gtag or Google
  4. Address any errors you find

Common Issues with Manual Implementation

Issue: _gl parameter not appearing in URLs

Causes:

  • The linker configuration is placed AFTER the config commands (fix: move it before)
  • Domain names are misspelled in the linker array
  • JavaScript errors preventing gtag from loading
  • Website redirects stripping URL parameters

Issue: Cookies not transferring

Causes:

  • Linker configuration not present on all pages of all domains
  • Cookie domain scope issues (some domains blocking third-party cookies)
  • Browser privacy settings blocking cross-site tracking

Issue: Code conflicts with existing tracking

Causes:

  • Multiple gtag.js library loads (you should only load it once)
  • Old Google Analytics (analytics.js or ga.js) conflicting with gtag.js
  • Other tag management solutions interfering

After seeing the manual implementation, you can understand why Google Tag Manager is strongly recommended:

With GTM:

  • No code changes needed to update tracking
  • Built-in preview mode for testing before publishing
  • Visual interface for configuration
  • Version control and easy rollback
  • One container code snippet on all pages (never changes)

With Manual Implementation:

  • Code changes required for every update
  • Testing requires publishing to production
  • Editing HTML files manually
  • No easy rollback if something breaks
  • Must update code on every page when changes needed

If you’re currently using manual implementation, consider migrating to Google Tag Manager for easier long-term maintenance.

Alternative: Consolidated Tag

This section covers the consolidated approach: one Google Tag managing multiple destinations. Use this if you’ve determined (from the decision framework earlier) that consolidated makes sense for your situation.

When to Use This Approach

Refer back to the “When Consolidated Makes Sense” section. In summary:

  • Extremely simple website with identical settings for all platforms
  • Absolute beginner (can refactor later)
  • Hard-coding tags without GTM
  • Rapid prototype or MVP
  • Single-person operation with no team complexity

Part A: GTM Implementation (Consolidated)

Step 1: Create or Modify Your Google Tag

If you’re starting from scratch:

  1. In GTM, click “Tags” > “New”
  2. Name it: “Google Tag – Consolidated”
  3. Click “Tag Configuration” > Select “Google Tag”
  4. Enter your primary Tag ID (typically your GA4 G- ID)

If you already have a Google Tag:

  1. Open your existing Google Tag
  2. Note your primary Tag ID
  3. Proceed to the next step

Verification Process: Making Sure It Actually Works

Implementation is only half the battle. Here’s how to thoroughly verify your cross-domain tracking is working correctly.

These tests work for both separate tags and consolidated tag approaches.

Test 1: GTM Preview Mode Testing (For GTM Users)

Step-by-Step GTM Preview Testing:

  1. Enter Preview Mode
    • In GTM, click “Preview” in the top right
    • Tag Assistant opens in a new tab
  2. Connect Primary Domain
    • Enter your primary domain URL (e.g., https://yourbrand.com)
    • Click “Connect”
    • Your site opens with a “Connected” badge in the corner
  3. Verify Tags Fire on Primary Domain
    • Go back to the Tag Assistant panel
    • Find the “Container Loaded” event
    • Expand “Tags Fired”
    • Verify your Google Tags appear with checkmarks:
      • For separate tags: “Google Tag – GA4” and “Google Tag – Google Ads”
      • For consolidated: “Google Tag – Consolidated” (or whatever you named it)
    • If tags show errors, click on them to see details
  4. Close Debugger but Keep Domain Enabled
    • Click the X to close the debugger view
    • IMPORTANT: Check “Keep the domain enabled for debugging”
    • Click “Close debugger”
  5. Add Secondary Domain
    • Click “Add domain” in Tag Assistant
    • Enter your secondary domain URL (e.g., https://secure-checkout.com)
    • Click “Connect”
  6. Navigate Between Domains
    • Go back to your primary domain tab
    • Click a link that takes you to the secondary domain
    • Watch the Tag Assistant panel as you navigate
    • You should see events appearing from both domains
  7. What to Look For
    • Events appear from both domains in Tag Assistant
    • Your Google Tags fire on both domains
    • No error messages in the event stream
    • Tags show green checkmarks, not red errors

If you see errors or tags not firing, investigate before publishing.

Test 2: The URL Parameter Check

This is the simplest and most critical test.

How to Test:

  1. Navigate from your primary domain to your secondary domain by clicking a link (not typing the URL)
  2. Look at the URL in your browser’s address bar on the secondary domain
  3. You MUST see a _gl parameter in the URL

What you should see:

https://secure-checkout.com/?_gl=1*abcde5*rs6h2f*MTcwOTkx...

The _gl parameter contains encrypted tracking information that links the sessions together.

If this parameter is missing, your cross-domain tracking is broken.

Common causes when missing:

  • Incorrect domain configuration in GTM
  • Website redirects stripping URL parameters
  • JavaScript redirects removing parameters
  • Linker configuration not set up correctly
  • Tags not firing before navigation occurs

This test verifies that Google Ads attribution data (the GCLID) is transferring correctly across domains.

Detailed Cookie Testing Process:

  1. Create a Test GCLID
    • Visit your landing page with a test GCLID parameter
    • Example: https://yourbrand.com/?gclid=testGCLID12345
    • Press Enter to load the page
  2. Check Cookie on Primary Domain
    • Open Developer Tools (Right-click > Inspect, or press F12)
    • Navigate to the “Application” tab (Chrome/Edge) or “Storage” tab (Firefox)
    • In the left menu, expand “Cookies”
    • Click on your primary domain
    • Find the _gcl_aw cookie in the list
    • Note its value – it should contain your test GCLID somewhere in it
    • Example value: GCL.1709912345.testGCLID12345
  3. Navigate to Secondary Domain
    • Click a link on your website that takes you to the secondary domain
    • Do NOT type the URL manually – you must click a link for cross-domain tracking to work
  4. Check Cookie on Secondary Domain
    • Once on the secondary domain, open Developer Tools again (F12)
    • Navigate to Application > Cookies
    • Select your secondary domain from the cookies list
    • Look for the _gcl_aw cookie
    • Compare its value to the value from the primary domain

Success Criteria: The _gcl_aw cookie must exist on the secondary domain with the EXACT same value as the primary domain.

If successful: Your cross-domain tracking is working perfectly. Google Ads will correctly attribute conversions on the secondary domain back to the original ad click.

If the cookie is missing or has a different value: Your setup needs troubleshooting. See the Troubleshooting section.

Test 4: Real-World Simulation

This end-to-end test confirms everything works under real conditions.

How to Test:

  1. Clear Your Data
    • Clear your browser cache and cookies completely
    • Or use an incognito/private browsing window
  2. Simulate a Real User Journey
    • Visit your primary domain with a test GCLID
    • Example: https://yourbrand.com/?gclid=testGCLID12345
    • Browse the site normally
    • Navigate to your secondary domain (checkout, thank you page, etc.)
    • Complete your conversion action if possible (test purchase, form submission, etc.)
  3. Check Google Ads Attribution
    • Wait 24-48 hours
    • Log into Google Ads
    • Navigate to Goals > Conversions
    • Look for your test conversion
    • Check the “Source” – it should show “Google Ads” or your campaign name
    • Should NOT show as “(direct)” or as a referral
  4. Check GA4 User Journey
    • Log into Google Analytics 4
    • Navigate to Reports > User > User Explorer
    • Find a recent user (yourself)
    • Expand the user journey
    • Verify you see pageviews from both domains in a single session
    • Should NOT show as two separate sessions

This confirms cross-domain tracking works in real-world conditions.

Test 5: Multiple Domain Journey

If your user journey involves more than two domains, test the full path:

  1. Start on Domain A with a test GCLID
  2. Navigate to Domain B (check for _gl parameter)
  3. Navigate to Domain C (check for _gl parameter)
  4. Verify cookies exist on all domains with matching values

Cross-domain tracking should work across any number of domains in your configuration.

Troubleshooting Failed Tests

If any test fails, refer to the Troubleshooting section (Section 9) for detailed debugging steps for each issue type.

Most common issues:

  • Tags firing after navigation occurs (use Initialization trigger)
  • Domain list mismatch between tags
  • Redirects stripping URL parameters
  • Cookie domain scope issues
  • Browser privacy settings blocking tracking

Step 2: Add Additional Destinations

  1. In the Google Tag configuration, find the “Destinations” section
  2. Click “Add Destination”
  3. Enter your additional ID:
    • If primary is GA4 (G-), add your Google Ads ID (AW- or GT-)
    • If primary is Google Ads (AW- or GT-), add your GA4 ID (G-)
  4. Click “Add” to confirm

You now have one tag managing both platforms.

Step 3: Configure Cross-Domain Tracking

  1. In the same Google Tag configuration, find “Configuration Settings”
  2. Click “Configure your domains”
  3. Add all domains in your user journey:
    • Click “Add condition”
    • Leave match type as “Contains”
    • Enter first domain: yourbrand.com
    • Click “Add condition” again
    • Enter second domain: secure-checkout.com
    • Repeat for all domains
  4. Click “Save” to close the domain configuration

This single configuration applies to ALL destinations.

Step 4: Handle Conversion Linker

If you have an existing Conversion Linker tag:

  1. Find it in your Tags list
  2. Click on it
  3. Click the three-dot menu > Select “Pause”
  4. Save

The Google Tag includes Conversion Linker functionality, so a separate tag is redundant.

Step 5: Set the Trigger

  1. Click “Triggering”
  2. Select “Initialization – All Pages”
  3. Save the tag

Step 6: Test and Publish

Follow the same preview and testing process described in the Separate Tags section (Step 4 of Part A).

The verification steps are identical:

  • Both destinations should receive data
  • _gl parameter should appear in cross-domain URLs
  • Cookies should transfer correctly

Part B: Manual Implementation (Consolidated)

If implementing gtag.js directly without GTM:

html

<!-- Google tag (gtag.js) -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXX"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());

  // CROSS-DOMAIN TRACKING - Must come before config commands
  gtag('set', 'linker', {
    'domains': ['yourbrand.com', 'secure-checkout.com']
  });

  // Single config command with multiple destinations
  gtag('config', 'G-XXXXXXX');  // GA4
  gtag('config', 'AW-XXXXXXX'); // Google Ads
</script>

The same principles apply:

  • Linker configuration before config commands
  • Single linker configuration applies to all destinations
  • Must be on all pages of all domains

Understanding the Trade-offs

What you gain:

  • Fewer tags to manage in GTM
  • Configure cross-domain once
  • Slightly cleaner tag list

What you sacrifice:

  • Harder troubleshooting (which destination has the issue?)
  • Shared configuration (can’t have different settings per platform)
  • Higher risk of breaking changes (affects all platforms simultaneously)
  • Less clear GTM Preview (one tag entry for multiple platforms)

Remember: If you find troubleshooting difficult or need independent configuration later, you can always migrate to separate tags. See the Migration Paths section for instructions.

Migration Paths

If you have existing tracking, here’s how to migrate to your desired end state.

Migration Checklist

Regardless of which migration path you follow, use this checklist:

Before Migration:

  • Document your current setup (screenshot your tags)
  • Note current conversion volume (baseline for comparison)
  • Identify all domains in your user journey
  • Back up your GTM container (Versions > Create Version)

During Migration:

  • Test thoroughly in Preview Mode before publishing
  • Verify tags fire on all domains
  • Verify _gl parameter appears in URLs
  • Verify cookies transfer correctly
  • Test with a real GCLID if possible
  • Document what changed in version notes

After Migration:

  • Monitor GA4 for 48-72 hours (check traffic levels)
  • Monitor Google Ads for 48-72 hours (check conversion volume)
  • Verify user journeys show continuity across domains
  • Check for any error spikes in tag firing
  • Compare metrics to pre-migration baseline

Rollback Plan:

  • Know how to revert to previous GTM version if needed
  • Keep old tags paused (not deleted) for at least 2 weeks
  • Monitor closely during first week after migration

Migration 1: From Setup A (Consolidated) → Separate Tags

If you currently have one Google Tag with multiple destinations and want to migrate to separate tags:

Step 1: Identify Your Current Configuration

  1. Open your existing consolidated Google Tag in GTM
  2. Note your primary Tag ID (e.g., G-XXXXXXX)
  3. Note your destination ID (e.g., AW-XXXXXXX)
  4. Note which domains are in your cross-domain configuration
  5. Keep this tag open for reference

Step 2: Create the First New Tag (GA4)

  1. Click “Tags” > “New”
  2. Name it: “Google Tag – GA4”
  3. Tag Configuration: Google Tag
  4. Tag ID: Your GA4 ID (G-XXXXXXX)
  5. Configure your domains: Copy the exact domain list from your consolidated tag
  6. Trigger: Initialization – All Pages
  7. Save (but don’t publish yet)

Step 3: Modify Your Existing Consolidated Tag (Convert to Google Ads Only)

  1. Go back to your consolidated tag
  2. Remove the GA4 destination (or Google Ads destination if your primary is Google Ads)
  3. You should now have only ONE ID in this tag
  4. Rename it: “Google Tag – Google Ads”
  5. Verify cross-domain settings are still configured
  6. Verify trigger is still “Initialization – All Pages”
  7. Save

Step 4: Test in Preview Mode

  1. Enter Preview Mode
  2. Connect your primary domain
  3. Verify BOTH tags now fire:
    • “Google Tag – GA4”
    • “Google Tag – Google Ads”
  4. Add your secondary domain to debugger
  5. Navigate between domains
  6. Verify _gl parameter appears
  7. Verify both tags fire on both domains

Step 5: Publish When Verified

  1. Exit Preview Mode
  2. Submit container with clear version notes
  3. Publish
  4. Monitor both platforms for 48-72 hours

Result: You now have separate tags with independent configurations.

Migration 2: From Setup B (GA4 + Conversion Linker) → Separate Tags

If you have a GA4 Google Tag and a Conversion Linker handling Google Ads:

Step 1: Verify Your GA4 Tag

  1. Open your existing GA4 Google Tag
  2. Verify cross-domain is configured
  3. If not configured, add your domains now
  4. Save if you made changes

Step 2: Create Google Ads Google Tag

  1. Click “Tags” > “New”
  2. Name it: “Google Tag – Google Ads”
  3. Tag Configuration: Google Tag
  4. Tag ID: Your Google Ads ID (AW- or GT-)
  5. Configure your domains: Use the SAME list as your GA4 tag
  6. Trigger: Initialization – All Pages
  7. Save

Step 3: Pause Conversion Linker

  1. Find your “Conversion Linker” tag
  2. Click on it
  3. Three-dot menu > Pause
  4. Save

Why pause it: The Google Ads Google Tag now includes Conversion Linker functionality, making the separate Conversion Linker redundant.

Step 4: Test and Publish

  1. Preview Mode
  2. Verify both Google Tags fire
  3. Verify cross-domain parameters work
  4. Publish when confirmed

Result: You’ve modernized to separate Google Tags.

Migration 3: From Setup C (Conversion Linker Only) → Separate Tags

If you only have Conversion Linker and old conversion tracking tags:

Step 1: Create GA4 Google Tag

  1. If you’re not already using GA4, set up a GA4 property first
  2. In GTM: Tags > New
  3. Name: “Google Tag – GA4”
  4. Tag Configuration: Google Tag
  5. Tag ID: Your GA4 ID (G-XXXXXXX)
  6. Configure your domains: List all domains in user journey
  7. Trigger: Initialization – All Pages
  8. Save

Step 2: Create Google Ads Google Tag

  1. Tags > New
  2. Name: “Google Tag – Google Ads”
  3. Tag Configuration: Google Tag
  4. Tag ID: Your Google Ads ID (AW- or GT-)
  5. Configure your domains: Same list as GA4 tag
  6. Trigger: Initialization – All Pages
  7. Save

Step 3: Pause Old Tags

  1. Find and pause your “Conversion Linker” tag
  2. Find your “Google Ads Conversion Tracking” tags
  3. Do NOT pause them yet – they’re still tracking conversions

Step 4: Test New Setup

  1. Preview Mode
  2. Verify both new Google Tags fire
  3. Verify old conversion tracking tags still fire
  4. Test cross-domain navigation
  5. Verify _gl parameter appears
  6. Test a conversion if possible

Step 5: Verify Conversion Tracking Still Works

  1. After testing in preview, publish
  2. Monitor Google Ads for 48-72 hours
  3. Verify conversions are still being recorded
  4. Compare conversion volume to historical data

Step 6: Optional Cleanup After confirming everything works for several days, you can optionally migrate your conversion tracking to GA4 events and import them to Google Ads. However, this is a larger project and beyond the scope of this cross-domain guide.

Result: You have modern Google Tags with cross-domain tracking, while maintaining existing conversion tracking.

Migration 4: Alternative Path → Consolidated Tag

If you currently have separate tags and want to consolidate (unusual but possible):

Step 1: Choose Your Primary Tag

  1. Decide which Google Tag will be your primary (usually GA4)
  2. Open that tag in GTM

Step 2: Add Other Destination

  1. In the tag configuration, find “Destinations”
  2. Click “Add Destination”
  3. Enter your other platform’s ID
  4. Save

Step 3: Remove/Pause Redundant Tags

  1. Pause your other Google Tag
  2. Pause any Conversion Linker tags
  3. Verify cross-domain configuration is present on the consolidated tag

Step 4: Test and Publish

  1. Preview Mode
  2. Verify single tag manages both destinations
  3. Test cross-domain navigation
  4. Publish when confirmed

Note: This migration path is not recommended for the reasons discussed in the Architecture Decision section, but it’s included for completeness.

Troubleshooting Common Issues

Even with careful implementation, cross-domain tracking can encounter issues. Here’s how to diagnose and fix the most common problems.

Debugging Tools

GTM Preview Mode: Primary debugging tool

  • Shows which tags fire, when, and with what data
  • Essential for diagnosis

Browser Developer Tools:

  • Console: JavaScript errors
  • Network: Tag loading and requests
  • Application: Cookie inspection
  • Source: Verify code presence

Google Tag Assistant (Chrome Extension):

  • Validates tag implementation
  • Shows tag firing sequence
  • Identifies common issues

GA4 DebugView:

  • Real-time event debugging for GA4
  • Navigate to Configure > DebugView in GA4
  • Requires debug mode enabled

Issue 1: _gl Parameter Not Appearing in URLs

Symptom: When navigating from primary to secondary domain, the URL doesn’t contain the _gl parameter.

This means: The linker is not decorating links, so sessions won’t connect across domains.

Diagnostic Steps:

  1. Verify Tags Fire Before Navigation
    • Open GTM Preview Mode
    • Navigate to primary domain
    • Look at “Container Loaded” event
    • Verify your Google Tags fire during this initial event
    • If tags fire later (like on “Click” events), they’re too late
    • Fix: Change trigger to “Initialization – All Pages”
  2. Check Cross-Domain Configuration
    • Open your Google Tag(s) in GTM
    • Click “Configure your domains”
    • Verify both domains are listed
    • Check for typos in domain names
    • Verify you’re using just the domain (no https:// or www. unless needed)
    • Fix: Add missing domains or correct typos
  3. Verify Domain Match Type
    • In cross-domain configuration, check the match type
    • Should be “Contains” for most cases
    • Fix: Change to “Contains” if set to something else
  4. Check for JavaScript Errors
    • Open browser Developer Tools (F12)
    • Go to Console tab
    • Look for red errors related to gtag or Google
    • Fix: Address any JavaScript errors preventing tags from loading
  5. Test Link Type
    • Cross-domain tracking works on link clicks, not all navigation types
    • Try different links on the page
    • Forms submitting across domains may need additional configuration
    • Fix: If using forms, enable “Decorate Forms” in tag settings (if available)
  6. Check for Redirects
    • Some redirects strip URL parameters
    • Use Network tab in Developer Tools to watch the navigation
    • Look for 301/302 redirects that might remove parameters
    • Fix: Modify redirect logic to preserve URL parameters, or use server-side redirect configuration

For Manual Implementation:

  • Verify gtag('set', 'linker', ...) is present
  • Verify it comes BEFORE gtag('config', ...) commands
  • Verify domain list is correct
  • Verify code is on all pages of all domains

Issue 2: Cookies Not Transferring

Symptom: The _gcl_aw cookie exists on primary domain but not on secondary domain (or has different value).

This means: Google Ads attribution data isn’t carrying over, so conversions won’t be attributed correctly.

Diagnostic Steps:

  1. First, Check if _gl Parameter Exists
    • If the _gl parameter isn’t in the URL, fix that first (see Issue 1)
    • Cookie transfer depends on the _gl parameter being present
  2. Verify Cookie Isn’t Being Blocked
    • Check if you’re using privacy/ad-blocking browser extensions
    • Try in an incognito window with no extensions
    • Try in a different browser
    • Fix: Test in clean browser environment
  3. Check Cookie Domain Scope
    • Open Developer Tools > Application > Cookies
    • Click on your primary domain cookie (_gcl_aw)
    • Check the “Domain” column
    • If it shows .yourdomain.com (with leading dot), it’s scoped to that domain tree
    • Fix: This is usually automatic, but if cookies are scoped incorrectly, it may be a browser or server configuration issue
  4. Verify Both Domains Accept Cookies
    • Some domains have restrictive cookie policies
    • Check browser console for cookie-related errors
    • Check if secondary domain has cookie consent barriers
    • Fix: Ensure both domains allow first-party cookies
  5. Check for Cookie Deletion
    • Some websites deliberately clear cookies on page load
    • Check if secondary domain has scripts that delete all cookies
    • Fix: Modify cookie clearing scripts to whitelist Google tracking cookies
  6. Timing Issues
    • Cookies need time to set
    • If navigation happens too quickly, cookies might not be ready
    • Fix: Usually not an issue with Initialization trigger, but verify tags fire early

For Google Ads Specifically:

  • Verify your Google Ads tag has the correct AW- or GT- ID
  • Verify the tag fires on all pages of all domains
  • Check Google Ads interface to ensure the conversion tracking tag is active

Issue 3: One Platform Working, Other Not

Symptom: GA4 data flows correctly across domains, but Google Ads conversions aren’t attributing. Or vice versa.

This is common with: Separate tags approach where one tag is misconfigured.

Diagnostic Steps:

  1. Identify Which Platform Has the Issue
    • Check GA4: Do you see continuous sessions across domains?
    • Check Google Ads: Are conversions attributing to campaigns or showing as “direct”?
  2. For the Broken Platform, Check Tag Firing
    • GTM Preview Mode
    • Navigate to both domains
    • Verify the specific platform’s tag fires on BOTH domains
    • If it only fires on one domain, the trigger may be wrong
    • Fix: Ensure trigger is “Initialization – All Pages” (not page-specific triggers)
  3. Verify Cross-Domain Configuration
    • Open the broken platform’s tag
    • Check if “Configure your domains” includes all domains
    • Compare to working platform’s domain list
    • They should match exactly
    • Fix: Add missing domains to the broken tag
  4. Check Tag ID
    • Verify you’re using the correct ID for that platform
    • GA4: Should start with G-
    • Google Ads: Should start with AW- or GT-
    • Fix: Correct the Tag ID if wrong
  5. Check for Conflicting Tags
    • Look for duplicate or conflicting tags
    • Multiple tags for the same platform can cause issues
    • Check for paused tags that should be deleted
    • Fix: Remove or pause conflicting tags

For Google Ads Specifically:

  • Verify conversion actions are set up in Google Ads interface
  • Check that conversion tags are firing (separate from the Google Tag)
  • Verify conversion actions are marked as “Primary” for reporting

Issue 4: Both Platforms Failing

Symptom: Neither GA4 nor Google Ads showing cross-domain tracking working.

This means: Something fundamentally wrong with the setup.

Diagnostic Steps:

  1. Start with Basic Tag Firing
    • GTM Preview Mode
    • Do your Google Tags fire at all on the primary domain?
    • If NO: Check that GTM container is installed on website
    • If YES: Proceed to next step
  2. Verify Tags Fire on Both Domains
    • In Preview Mode, test both domains
    • Do tags fire on primary domain but not secondary?
    • Fix: GTM container might not be installed on secondary domain
  3. Check GTM Container Installation
    • View source code on both domains
    • Search for your GTM container ID (GTM-XXXXXX)
    • Should appear in both <head> and <body> sections
    • Should be on all pages of all domains
    • Fix: Install GTM container on missing domain
  4. Verify Cross-Domain Configuration Exists
    • Open each Google Tag
    • Check if “Configure your domains” has any domains listed
    • If empty, that’s your problem
    • Fix: Add all domains to the configuration
  5. Check for JavaScript Errors
    • Open browser console
    • Look for errors preventing gtag from loading
    • Common: Library load failures, syntax errors, conflicts
    • Fix: Resolve JavaScript errors
  6. Test with Clean Browser
    • Use incognito mode
    • Disable all browser extensions
    • Try different browser
    • Fix: If works in clean browser, issue is browser-specific (extensions, settings)

For Manual Implementation:

  • Verify gtag.js code is on ALL pages of ALL domains
  • Verify linker configuration exists and is before config commands
  • Verify no typos in the code
  • Check browser console for loading errors

Issue 5: Working in Preview, Failing in Production

Symptom: Everything works perfectly in GTM Preview Mode, but fails after publishing.

This is frustrating but has specific causes:

Diagnostic Steps:

  1. Verify Container Published
    • Check GTM Versions tab
    • Ensure your latest changes are in the “Published” version
    • Not just “Latest Version”
    • Fix: Publish the container if not published
  2. Check for Caching Issues
    • Website might be serving cached version without new tags
    • Clear website cache (if using caching plugin/CDN)
    • Clear browser cache
    • Test in incognito mode
    • Fix: Wait for cache to clear, or force cache invalidation
  3. Check GTM Container Code
    • View source on live site
    • Verify GTM container is present and correct
    • Check that container ID matches your published container
    • Fix: If wrong container or missing, update website code
  4. Verify Tag Permissions
    • Some tags require specific permissions
    • Check GTM tag permissions settings
    • Fix: Grant necessary permissions if blocked
  5. Check for Publishing Conflicts
    • If multiple people use GTM, someone might have published over your changes
    • Check version history
    • Fix: Re-publish your version

Issue 6: Intermittent Failures

Symptom: Sometimes works, sometimes doesn’t. Inconsistent behavior.

Common causes:

  1. Race Conditions
    • Tags fire after user already navigated
    • Use “Initialization” trigger (not “Page View” or later)
    • Fix: Change trigger to “Initialization – All Pages”
  2. Slow Page Load
    • On slow connections, tags might not load before user clicks
    • Fix: Ensure GTM container in <head> section, not footer
  3. Mobile vs Desktop
    • Works on desktop but not mobile (or vice versa)
    • Check if website serves different code for mobile
    • Fix: Ensure tracking code on all versions of site
  4. Browser-Specific
    • Works in Chrome but not Safari
    • Safari has stricter privacy controls
    • Fix: Test in multiple browsers; ensure not relying on blocked features
  5. Network Issues
    • Google’s servers unreachable in some regions
    • Usually temporary
    • Fix: Monitor, usually resolves itself

When to Get Help

If you’ve tried these troubleshooting steps and still have issues:

  1. Document what you’ve tested
    • Screenshots of Preview Mode
    • URLs showing missing parameters
    • Cookie values from Developer Tools
    • Any error messages
  2. Check Google’s Official Documentation
    • Search Google Tag Manager help center
    • Check Google Ads help center
    • Look for recent known issues
  3. Post in Communities
    • r/GoogleTagManager on Reddit
    • Google Tag Manager Community Forum
    • Include specific details, not just “it doesn’t work”
  4. Consider Professional Help
    • If this is business-critical, consider hiring a GTM expert
    • Cross-domain tracking issues can have subtle causes
    • Professional diagnosis often pays for itself in saved time

The Bottom Line

Cross-domain tracking might seem technical, but it’s fundamentally about one thing: getting credit for the sales and leads your ads actually generate.

In an era where every marketing dollar must be justified, accurate attribution isn’t optional – it’s survival. The businesses that master cross-domain tracking will have a significant competitive advantage in optimizing their Google Ads spend.

Architectural Choice Matters

A final word on architecture: While this guide shows you how to implement both consolidated and separate tag approaches, my hands-on experience troubleshooting cross-domain tracking has taught me that separate tags provide dramatically easier troubleshooting and more flexibility.

Google pushes consolidation for marketing simplicity, but practitioners often need architectural clarity more than tag count reduction. Don’t be afraid to choose the approach that makes your life easier, even if it’s not what the official documentation emphasizes.

Choose clarity over consolidation. Your future self will thank you when you’re diagnosing issues at 3 AM.

The Competitive Advantage

Most advertisers never properly implement cross-domain tracking. They lose attribution, make decisions on bad data, and wonder why their campaigns underperform.

By implementing this correctly, you’re gaining an advantage:

  • More accurate conversion attribution
  • Better optimization decisions
  • Clearer understanding of user journeys
  • Proper ROI calculation

This isn’t just technical configuration – it’s a competitive moat.

Conclusion

Don’t let broken tracking silently sabotage your ROI. Take action today, implement proper cross-domain tracking, and discover the true performance of your Google Ads campaigns.

And remember: when in doubt, test everything twice. The 30 minutes you spend verifying now saves you hours of troubleshooting later.

Good luck with your implementation. You’ve got this.

Leave a Comment

Your email address will not be published. Required fields are marked *

Navigation