Cross-Domain Tracking GA4: The 2026 Setup Guide

By Rafirit Station Editorial Team · Updated 2026 · ⏱ 12 min read

Cross-domain tracking in GA4 is essential for businesses with multiple domains or subdomains. According to a 2025 industry report by MeasureSchool, 67% of GA4 users have misconfigured cross-domain tracking, leading to 20-30% data loss in user journeys.

As GA4 fully replaces Universal Analytics, accurate cross-domain tracking is more critical than ever. Without it, your attribution data is fragmented, and you miss out on understanding the complete customer path across separate websites.

For a Dhaka-based e-commerce brand, this could mean losing ৳7,00,000 in attributed revenue annually. Every user who moves from your blog to your main store without being tracked as a single session results in inflated new user counts and broken conversion paths.

After reading this guide, you will know exactly how to set up cross-domain tracking in GA4 for subdomains, separate domains, and microsites – ensuring 100% accurate session unification starting today.

📚 External Resources (Bookmark These)

• Google Analytics Help: Cross-domain tracking
• Google Developers: GA4 cross-domain setup
• HubSpot Blog: GA4 Cross-Domain Tracking
• Moz: GA4 Cross-Domain Tracking Guide
• Semrush: Cross-Domain Tracking GA4
• Ahrefs: Cross-Domain Tracking
• Backlinko: GA4 Cross-Domain Tracking
• Shopify Blog: Cross-Domain Tracking
• Search Engine Land: GA4 Cross-Domain Guide
• Neil Patel: Cross-Domain Tracking

🔗 Rafirit Station Services

• Web Analytics — GA4 & GTM setup
• Web Analytics Dhaka — Local analytics team
• CRO Services — Use data to convert more
• SEO Services — Measure & grow organic traffic
• Google Ads Management — Data-driven PPC
• Case Studies — Analytics-driven results
• Packages & Pricing
• Rafirit Station Bangladesh — Digital Agency
• Rafirit Station Dhaka — Full-Service Agency

Phase 1: Preparation and Prerequisites

Before diving into GA4 settings, you need a clear picture of your domain architecture and access rights. This phase ensures you don’t miss any critical configurations.

Tactic 1.1: Audit Your Current Domain Setup

Why this works: Many businesses underestimate the number of domains involved. A thorough audit reveals hidden microsites, subdomains, and third-party platforms that need tracking.

Exactly how to do it:

1. List all domains and subdomains your business owns (e.g., yourmainstore.com, blog.yourmainstore.com, checkout.yourpayment.com).
2. Identify any third-party services (e.g., a booking system on another domain).
3. Document the starting URLs and conversion pages for each.
4. Check if you already have GA4 or GTM installed on each property.
5. Create a diagram showing user flow across these properties.
6. Note any existing referral exclusions or cross-domain settings in Universal Analytics that need migration.

Pro script / template: Use a spreadsheet with columns: Domain, GA4 Measurement ID, GTM Container ID, Current Cross-Domain Status, Notes.

📊 Expected results: A complete inventory within 2 hours. This prevents 80% of setup mistakes.

Tactic 1.2: Understand GA4’s Measurement ID and Configurations

Why this works: GA4 uses a single Measurement ID per data stream. Cross-domain tracking is configured at the stream level, so you must know which streams connect to which domains.

Exactly how to do it:

1. Go to GA4 Admin > Data Streams and note each stream’s Measurement ID (e.g., G-XXXXXXXXXX).
2. Identify which streams correspond to which domains.
3. Ensure you have Admin access to all GA4 properties involved.
4. Decide if you will use a single stream for multiple domains (recommended) or separate streams.

Pro script / template: For a unified view, use one data stream for your primary domain and add all others via cross-domain settings. This keeps reporting simple.

📊 Expected results: Clear mapping of streams to domains, reducing confusion during setup.

Tactic 1.3: Plan Your Cross-Domain Architecture

Why this works: A deliberate architecture prevents later conflicts. For example, subdomains (blog.site.com) and separate domains (site2.com) require different handling.

Exactly how to do it:

1. Decide which domains will share a single user session (e.g., main site and checkout).
2. Determine whether subdomains are automatically included (they are not by default; you must add them like separate domains).
3. Plan for referral exclusions to prevent self-referrals.
4. Consider using Google Tag Manager for advanced control if needed.

Pro script / template: If you have a subdomain like shop.example.com, you must add “example.com” and “shop.example.com” to the cross-domain list GA4 expects both.

📊 Expected results: A two-page document outlining your architecture, ready for implementation.

Phase 2: Implementing Cross-Domain Tracking via GA4 Settings

This is where the actual configuration happens. Follow each step carefully.

Tactic 2.1: Add Domains to GA4 Admin > Data Streams > Configure Tag Settings

Why this works: GA4’s built-in cross-domain setting tells the tracking code to stitch sessions when a user moves between listed domains.

Exactly how to do it:

1. In GA4, go to Admin > Data Streams and select your web data stream.
2. Click “Configure tag settings” (or “Tag settings”).
3. Scroll to “Cross-domain measurement” and click “Add condition”.
4. Choose “Include domains that match” and enter the domain names (e.g., example.com, sub.example.com, otherdomain.com).
5. Click “Create” and save.
6. Repeat for each stream that should share sessions (if using multiple streams).

Pro script / template: Enter domains without “http” or “www” – just the naked domain (e.g., example.com). For subdomains, list them explicitly.

📊 Expected results: Sessions now persist across listed domains, visible in GA4 reports within 24 hours.

Tactic 2.2: Set Up Referral Exclusion

Why this works: Without referral exclusions, traffic between your own domains appears as referral traffic, breaking attribution. This is the most commonly missed step.

Exactly how to do it:

1. In GA4 Admin, go to “Data collection and modification” > “Referral exclusions”.
2. Click “Add referral exclusion”.
3. Enter each domain that you added in cross-domain settings (e.g., example.com).
4. Optionally, add subdomains if they appear as referrers.
5. Save each exclusion.

Pro script / template: Add all domains from your list, including variations like www.example.com and example.com.

📊 Expected results: Self-referrals drop by 90% within 48 hours, giving cleaner source/medium data.

Tactic 2.3: Test with GA4 DebugView

Why this works: DebugView shows real-time events with a debug mode, letting you verify that cross-domain linking works.

Exactly how to do it:

1. Open your website with ?gtm_debug=x or enable preview in GTM.
2. Navigate from one domain to another.
3. Go to GA4 Admin > DebugView (in the same property).
4. Check that the session ID remains the same across domains (look for the same session_id parameter).
5. Confirm that events are attributed to the same user.

Pro script / template: Use the Chrome extension “Google Analytics Debugger” to enable debug mode easily.

📊 Expected results: Instant verification; if session ID changes, your configuration is incomplete.

Tactic 2.4: (Optional) Use Google Tag Manager for Additional Control

Why this works: GTM allows you to set cross-domain tracking via the GA4 Configuration tag, offering more flexibility for complex setups.

Exactly how to do it:

1. In GTM, open your GA4 Configuration tag.
2. Under “Fields to Set”, add a field: “linker” with value “true”.
3. Add another field: “linker_domains” with value as a comma-separated list of domains.
4. Publish the container.

Pro script / template: In the Configuration tag, set:
– Field name: linker, Value: true
– Field name: linker_domains, Value: example.com,sub.example.com,other.com

📊 Expected results: Full control over cross-domain behavior, useful when you need to track across multiple websites under different GTM containers.

Phase 3: Advanced Configuration for Complex Setups

For businesses with multiple brands, microsites, or international domains, these tactics address edge cases.

Tactic 3.1: Handling Subdomains vs. Separate Domains

Why this works: Subdomains are often assumed to be automatically tracked together, but GA4 treats them as separate origins. Adding them ensures session continuity.

Exactly how to do it:

1. Add subdomains (e.g., blog.example.com) to the cross-domain list in GA4, just like separate domains.
2. Also add the root domain (example.com).
3. Set up referral exclusions for all subdomains.

Pro script / template: If you use a subdomain for a regional site (us.example.com), include it in the list to avoid session breakage.

📊 Expected results: Users moving from blog.example.com to example.com maintain a single session.

Tactic 3.2: Using URL Passthrough for Enhanced Measurement

Why this works: URL passthrough appends parameters (_gl) to URLs when users cross domains, helping GA4 link sessions without relying on cookies.

Exactly how to do it:

1. In GA4 Admin > Data Streams > Configure tag settings > Cross-domain measurement, ensure “URL passthrough” is enabled.
2. Automatically, _gl parameter is added to links.
3. Verify that your server-side redirects preserve these parameters.

Pro script / template: If you use server-side redirects, ensure the _gl parameter is passed along, otherwise sessions will break.

📊 Expected results: Higher session linkage rate, especially in browsers with third-party cookie restrictions.

Tactic 3.3: Multi-Domain eCommerce Tracking

Why this works: For eCommerce, you need to track the purchase event across the entire funnel, even if it spans multiple domains.

Exactly how to do it:

1. Implement the same GA4 data stream or GTM container across all domains in the funnel.
2. Enable cross-domain measurement as above.
3. Use enhanced eCommerce events consistently (view_item, add_to_cart, purchase).
4. Verify that the purchase event contains the same session ID as the earlier events.

Pro script / template: Test by adding an item to cart on domain A, then completing checkout on domain B. The purchase should attribute to the original traffic source.

📊 Expected results: Accurate attribution for multi-domain funnels, reducing last-click bias.

Phase 4: Verification and Maintenance

Setup is not the end; you must continuously verify that cross-domain tracking works correctly.

Tactic 4.1: Validate with Real User Sessions

Why this works: DebugView might work in ideal conditions, but real traffic reveals edge cases (e.g., browser quirks, redirects).

Exactly how to do it:

1. Use the “User Explorer” report in GA4 to find users who visited multiple domains.
2. Check the session start time and session ID across hits.
3. Look for unexpected new sessions when users cross domains.
4. If you see multiple session starts, your setup is incomplete.

Pro script / template: Filter User Explorer for users who have events from two different domains (e.g., example.com and other.com).

📊 Expected results: Within 48 hours, you can confirm session continuity for 90%+ of users.

Tactic 4.2: Monitor Cross-Domain Activity in Reports

Why this works: Regular monitoring helps spot issues early, like a domain being added without referral exclusion.

Exactly how to do it:

1. Create a custom report in GA4 showing events by domain.
2. Check the “Cross-domain” dimension (if available) or use secondary dimension “Hostname”.
3. Look for spikes in sessions from your own domains (a sign of broken referral exclusion).

Pro script / template: Set an alert in GA4 for unusual referral traffic from your own domains.

📊 Expected results: Early detection of misconfigurations, saving weeks of data contamination.

Tactic 4.3: Regular Audits and Updates

Why this works: Domains change – you may add a new microsite or remove an old one. Weekly audits keep tracking accurate.

Exactly how to do it:

1. Every month, review your cross-domain list and referral exclusions.
2. Check for any new domains or subdomains that have been launched.
3. Remove any defunct domains.
4. Re-test using DebugView after any changes.

Pro script / template: Set a calendar reminder for the first Monday of each month to audit cross-domain settings.

📊 Expected results: 100% accuracy over time, avoiding data drift.

🏆 Real Case Study: How a Dhaka-Based Business Achieved 40% Lift in Attributed Revenue

Client: BanglaTrends, a Dhaka-based fashion e-commerce brand with separate blog (blog.banglatrends.com) and main store (banglatrends.com), plus a payment partner domain (securepayment.com).

Before (Q1 2025): GA4 showed 22% new user rate from blog to store, with average order value ৳1,200. Many blog visitors were recorded as new users when they moved to the store, breaking the conversion path. Attributable revenue was ৳15,00,000/month, but they suspected underreporting.

Our strategy:

• Audited all domains and added blog.banglatrends.com, banglatrends.com, and securepayment.com to GA4 cross-domain settings.
• Set up referral exclusions for all three domains.
• Used URL passthrough to ensure session linking even with third-party payment redirect.
• Implemented GTM across all domains with a single GA4 Configuration tag and linker fields.
• Trained team on monthly audits.

After (Q2 2025): Within 30 days, attributed revenue jumped to ৳21,00,000/month – a 40% increase. Secondary improvements: new user rate from blog dropped to 5%, average order value rose to ৳1,350, and session duration increased 25% as users moved seamlessly.

Client quote: “We knew we were losing data, but seeing a 40% revenue lift after fixing cross-domain tracking was eye-opening. Rafirit Station made the process smooth.” — Mahmud Hasan, CTO BanglaTrends

See more Rafirit Station case studies →

✅ Cross-Domain Tracking GA4 Setup Checklist

❓ Frequently Asked Questions

🎯 The Bottom Line

Cross-domain tracking in GA4 is not just a technical checkbox; it’s the foundation of accurate attribution. Without it, your marketing reports are unreliable, and you’re making decisions based on incomplete data. The counterintuitive insight? Adding domains to GA4 is not enough – referral exclusions are equally critical, and subdomains must be explicitly included.

Investing the time to set this up correctly – or partnering with experts like Rafirit Station – pays off immediately. In our experience, most businesses see at least a 20% lift in attributed conversions after proper implementation.

⚡ Your Next Step (Do This Today)

1. List your business’s domains and subdomains (take 10 minutes).
2. Check if GA4 cross-domain measurement is already configured (check GA4 Admin > Data Streams > Configure tag settings).
3. Add any missing domains and set up referral exclusions (30 minutes).
4. Enable URL passthrough if not already on (5 minutes).
5. Test with DebugView by navigating from one domain to another (15 minutes).

💬 Drop “CROSS-DOMAIN” in the comments and we’ll send you our free GA4 cross-domain tracking checklist — no email required.