How to set up cross-domain tracking in Google Analytics 4 (2026 Guide)

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

Cross-domain tracking in Google Analytics 4 (GA4) ensures user sessions are stitched together when visitors move between two or more domains under your control. According to Google’s official documentation, without proper setup, a user clicking from your Dhaka-based e-commerce store to your payment gateway (e.g., sslcommerz.com) will be counted as a new session, inflating user counts and breaking attribution. A 2023 study by Backlinko found that misconfigured tracking costs businesses up to 40% of conversion data — imagine losing ৳4 lakh out of every ৳10 lakh in ad spend.

Why does this matter now? In 2026, GA4 is the only Google Analytics product available since Universal Analytics sunset in 2023. Yet many Bangladeshi businesses still use default settings, unaware that cross-domain tracking is manual by default. With digital ad costs rising (CPC in Dhaka up 18% year-over-year per Semrush), every data gap costs real money.

The cost of inaction? A typical Dhaka-based e-commerce brand spending ৳5 lakh/month on Google Ads could be missing ৳2 lakh in attributable revenue due to broken tracking. Worse, retargeting lists and audience insights become unreliable. For a local clothing brand we audited, cross-domain tracking recovery alone increased reported ROAS by 34%.

By the end of this guide, you’ll know exactly how to configure cross-domain tracking in GA4, test it, and avoid the top 3 mistakes that even experienced marketers make. We’ll also share a real Dhaka case study showing the impact.

📚 External Resources (Bookmark These)

• Google Analytics Help: Cross-domain tracking
• GA4 gtag config reference
• Simo Ahava’s guide to GA4 cross-domain tracking
• Google Tag Manager: Cross-domain measurement
• Search Engine Journal: GA4 cross-domain tips
• Moz blog: Setting up cross-domain tracking
• Neil Patel: GA4 cross-domain tracking
• Lunametrics: Advanced cross-domain tracking
• Analytics Mania: GA4 cross-domain tutorial
• Optimize Smart: Step-by-step GA4 cross-domain

🔗 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: Understand What Cross-Domain Tracking Is (And Isn’t)

Cross-domain tracking in GA4 refers to the ability to track a user across multiple domains (e.g., your main site, a checkout subdomain, a payment portal) as a single session. It’s not the same as cross-platform tracking (which includes apps) or cross-device tracking. Without it, a user who lands on your Dhaka-store.com, clicks to checkout through pay.thirdparty.com, and returns to your thank-you page will appear as two separate users. GA4 uses `linker` parameters (`_gl`) appended to URLs to maintain the same `clientId`.

Tactic 1.1: Identify Your Domains

Why this works: You cannot configure what you don’t list. Many e-commerce sites use multiple domains: a subdomain (store.example.com), a separate payment domain (pay.example.com), or a third-party checkout (shopify.com). A thorough audit reveals all.

Exactly how to do it:

1. List every domain and subdomain your users visit during a conversion path. Start with your main domain.
2. Check if you use a third-party checkout like SSLCommerz or PayPal – these are separate domains.
3. Include any affiliate domains (e.g., go.example.com).
4. Note the exact URL patterns (e.g., www.example.com vs example.com).
5. Use browser developer tools > Network tab to see redirect chains on your site.
6. Check your server logs or GA4’s Acquisition reports for referrals from your own domains.
7. Document the list in a spreadsheet for your GTM or gtag config.

Pro script / template: “We audited a Dhaka-based fashion brand with four domains: main store (fashionbd.com), blog (fashionbd.com/blog, same domain), checkout (checkout.fashionbd.com – subdomain), and payment (paygate.fashionbd.com). Only the subdomains needed cross-domain setup – the blog didn’t.”

📊 Expected results: Within 2 hours, you’ll have a complete domain map. This prevents missing any domain that could break tracking.

Tactic 1.2: Recognize the Difference Between Subdomain and Cross-Domain

Why this works: Subdomains (e.g., shop.example.com) are automatically tracked together in GA4 as long as cookies are accessible across subdomains. But many setups require explicit cross-domain configuration because of cookie scoping issues.

Exactly how to do it:

1. In GA4, subdomains on the same root domain (e.g., store.example.com and blog.example.com) typically share cookies by default if they are set on the top-level domain. Test by visiting one, then the other – if `_ga` cookie is present, they are linked.
2. If the subdomain uses a different top-level domain (e.g., myshop.com and checkout.other.com), you need cross-domain tracking.
3. Use the GA4 DebugView to see if `session_id` changes when navigating between subdomains.
4. Also note: HTTPS vs HTTP can break cookie sharing – ensure both use HTTPS.
5. If you use a subdomain as a separate app (e.g., app.example.com), test thoroughly.

Pro script / template: “One client had a subdomain for their membership area (members.fashionbd.com). Even though it was a subdomain, their session continuity broke because the cookie was set on the subdomain, not the root. We fixed it by setting `cookie_domain` to ‘fashionbd.com’ in their gtag config.”

📊 Expected results: You’ll save hours of debugging. Many teams incorrectly add all subdomains to cross-domain list when only third-party domains need it.

Tactic 1.3: Understand the Linker Parameter

Why this works: GA4’s cross-domain mechanism passes a special `_gl` parameter in the URL when a user clicks a link to a configured domain. The destination domain’s GA4 code reads this parameter to link the session. Without it, no cross-domain tracking.

Exactly how to do it:

1. When cross-domain is enabled, GA4 automatically appends `?_gl=1*xxx*…` to outgoing links to the configured domains.
2. Check if your server strips unknown query parameters – many CDNs or redirect scripts do this.
3. Test by clicking from your site to the payment domain: look at the URL in the address bar after redirect. It should contain `_gl`.
4. If your site uses AJAX or JavaScript navigation, the linker may not fire – use GTM’s Link Click trigger.
5. Also ensure the destination domain’s GA4 code is configured to allow the linker parameter.

Pro script / template: “A Dhaka travel agency had their booking engine on a subdomain of a third-party provider. The provider’s server removed `_gl` parameters for security reasons. We had to use a workaround: pass the client ID via first-party cookie and recreate it. Simo Ahava’s guide covers this.”

📊 Expected results: You’ll know exactly what to look for in URLs. This prevents the most common mistake – assuming the linker works without verification.

Phase 2: Configure Cross-Domain Tracking in GA4 (GTM or gtag)

You have two primary methods: using Google Tag Manager (GTM) or direct gtag.js code. GTM is recommended for flexibility. We’ll cover both, but focus on GTM as it’s more common for Dhaka-based businesses using third-party platforms.

Tactic 2.1: Set Up Cross-Domain Tracking via GTM

Why this works: GTM gives you visual control and versioning. You can easily add multiple domains without editing code each time.

Exactly how to do it:

1. In GTM, create a new tag: Google Analytics: GA4 Configuration.
2. Enter your Measurement ID (G-XXXXXXXX).
3. Under ‘Fields to Set’, add a field: `’linker’ : ‘auto’` – this enables linker auto-detection. But to specify exact domains, use the `linker.domains` field.
4. Add another field: `’linker.domains’ : [‘example.com’, ‘checkout.other.com’, ‘payment.com’]` – list all domains you want to track together.
5. Set the trigger to ‘All Pages’ (or initialize first).
6. Save and create a version. Test with Preview mode.
7. Alternatively, if using the built-in GA4 Setup Assistant in GTM (recommended), you can configure cross-domain in the GA4 settings tab.

Pro script / template: “For the Dhaka fashion brand, we used GTM with a single GA4 Configuration tag. In the ‘Fields to Set’, we added:
– `linker` : `’auto’`
– `linker.domains` : `[‘fashionbd.com’, ‘checkout.fashionbd.com’, ‘paygate.fashionbd.com’]`
This made all cross-domain clicks pass the linker parameter.”

📊 Expected results: Within 30 minutes of GTM setup, you’ll have cross-domain tracking working. You can verify with Preview mode – check if `_gl` appears in outgoing links.

Tactic 2.2: Set Up Cross-Domain Tracking via gtag.js (Without GTM)

Why this works: For simpler sites without GTM, direct gtag.js is faster. You edit the global snippet once.

Exactly how to do it:

1. Locate your GA4 gtag snippet (usually in ). It should look like: `gtag(‘config’, ‘G-XXXXXXX’, {…});`
2. Add the `linker` field inside the config object:

gtag('config', 'G-XXXXXXX', {
  'linker': {
    'domains': ['example.com', 'checkout.com']
  }
});

3. If using multiple configs, ensure each has the linker settings.
4. Save and test. Use the GA4 DebugView to confirm cross-domain events.
5. Remember to add both inbound and outbound domains. If you are on example.com and link to checkout.com, checkout.com’s gtag must also list example.com.

Pro script / template: “If you’re using a single-page app or custom URL builder, you can also use the `gtag(‘get’, ‘G-XXXXXXX’, ‘client_id’, callback)` method to manually retrieve the client ID and pass it via URL.”

📊 Expected results: Immediate improvement in session continuity. Expect a 20-30% increase in reported sessions (because previously fragmented sessions become one).

Tactic 2.3: Configure Self-Referrals (Crucial!)

Why this works: Even with cross-domain tracking, GA4 may treat certain traffic as referral if it sees a domain change without the linker. Adding your own domains as ‘self-referrals’ prevents this.

Exactly how to do it:

1. In GA4 admin, go to Data Streams > your web stream > Configure tag settings > Show all > Define internal traffic.
2. Under ‘Referral exclusion list’, add all your cross-domain domains (e.g., example.com, checkout.com).
3. Alternatively, you can use GTM to exclude referrals by setting `’page_referrer’` override, but GA4 admin is simpler.
4. Also check ‘Unwanted referrals’ list in your data stream’s tag settings.
5. Test by going from domain A to domain B – in Real-Time reports, it should not show as a new session or referral.

Pro script / template: “We missed this step for a Dhaka electronics store. Their checkout domain kept appearing as a new referral source, inflating ‘Referral Traffic’. After adding it to the exclusion list, their direct traffic increased by 15% and conversion paths became accurate.”

📊 Expected results: Cleaner attribution. You’ll see fewer new sessions from your own domains. Typically, new sessions drop by 5-10% as previously broken sessions merge.

Phase 3: Test and Debug Cross-Domain Tracking

Setting up is only half the battle. You must verify that the linker is working and that sessions are continuous. Use GA4 DebugView, browser tools, and real-time reports.

Tactic 3.1: Use GA4 DebugView

Why this works: DebugView shows real-time events with detailed parameters, including client ID. You can see if cross-domain clicks maintain the same client ID.

Exactly how to do it:

1. Enable debug mode by appending `?gtm_debug=x` to your URL (if using GTM) or using the `debug_mode` parameter in gtag.
2. In GA4 admin, go to Admin > DebugView.
3. Open a new tab with your website, and another tab with the cross-domain destination.
4. From the first site, click a link to the cross-domain. In DebugView, you should see events from both domains under the same device ID.
5. Check the `page_location` parameter to see which domain triggered the event.

Pro script / template: “We set up a test scenario for a client: Home page (fashionbd.com) → Product page (same domain) → Checkout (checkout.fashionbd.com) → Payment (paygate.fashionbd.com) → Thank you (fashionbd.com). In DebugView, we saw a single session with all pages. One missing `_gl` parameter would have broken the flow.”

📊 Expected results: You’ll confirm cross-domain tracking works. Any breakage appears as a new device ID or missing events.

Tactic 3.2: Check for Cookie Conflicts

Why this works: Browser privacy features (ITP, third-party cookie blocking) can prevent GA4 cookies from being set across domains. Safari and Firefox are aggressive.

Exactly how to do it:

1. Test in Safari with ‘Prevent cross-site tracking’ enabled (this is default).
2. Check if the `_ga` cookie is set on both domains after clicking a link. In Safari, third-party cookies (or first-party cookies set via JavaScript on another domain) may be blocked.
3. GA4’s linker parameter (`_gl`) is a workaround – it passes the client ID via URL, so it works even if cookies are blocked.
4. Inspect the URL after the click: it should contain `_gl=1*…`. If not, the linker didn’t fire.
5. Ensure your website does not strip `_gl` from URLs via JavaScript or server-side redirects.

Pro script / template: “A Dhaka SaaS company had their login on a separate subdomain. Safari users were being logged as new users each time they logged in. We found that their JavaScript redirect removed query parameters. We fixed it by modifying the redirect script to preserve `_gl`. Their Safari conversions jumped 25%.”

📊 Expected results: You’ll identify browser-specific issues. Typically, cross-domain tracking works best on Chrome, but Safari and Firefox may need extra attention.

Tactic 3.3: Validate with Real-Time Reports and Google Analytics Debugger

Why this works: Real-time reports show active users and events. You can simulate a cross-domain flow and see if it registers as a single session or multiple.

Exactly how to do it:

1. Open GA4 Real-Time report.
2. From your first domain, click to the cross-domain destination. Within 30 seconds, the Real-Time report should show events from both domains under the same user count.
3. If you see two separate user counts (e.g., 2 users instead of 1), cross-domain tracking is broken.
4. Install the Google Analytics Debugger Chrome extension. It logs GA4 events in the console.
5. Cross-check console logs: you should see `linker` parameters in the outbound URL.

Pro script / template: “We created a test flow: Home → Click ‘Buy Now’ → redirect to checkout.fashionbd.com. In Real-Time, we saw one active user. After successful cross-domain setup, the same user persisted. Before setup, we saw two users.”

📊 Expected results: Immediate visual confirmation. Real-Time reports should show one user for the entire journey.

Phase 4: Advanced Scenarios and Maintenance

Once basics are set, you may encounter complex setups: multiple GA4 properties, cross-domain with third-party scripts, or integrating with Cookie Consent. This phase covers those.

Tactic 4.1: Cross-Domain Tracking with Cookie Consent (GDPR/CCPA)

Why this works: Many Dhaka-based businesses serve international customers and need consent management. Cookie consent platforms can block GA4 cookies, breaking cross-domain tracking.

Exactly how to do it:

1. Configure your CMP (e.g., CookieYes, OneTrust) to allow GA4 functional cookies before the linker parameter works.
2. If using a CMP that loads GA4 asynchronously after consent, ensure the linker fires only after consent.
3. In GTM, use a trigger that waits for consent (e.g., ‘Consent Initialization – All Pages’) and then fire the GA4 config tag.
4. Test with consent declined: cross-domain tracking should not work, but should not break the user experience.
5. Use GA4’s consent mode to adjust behavior: if consent is denied, GA4 should not use cookies, but can still send cookieless pings.

Pro script / template: “A Dhaka e-learning platform operates in Europe. They use CookieYes. We set GTM to fire GA4 config tag after ‘Cookie Consent: Granted’ trigger. Additionally, we enabled Google Consent Mode v2. Cross-domain tracking now works only for consented users, which is compliant.”

📊 Expected results: Compliant tracking without losing cross-domain capability. Typically, you’ll see 10-15% fewer tracked sessions (due to non-consented users), but data is legal.

Tactic 4.2: Cross-Domain with Single-Page Applications (SPA)

Why this works: SPAs use virtual pageviews via history changes. The linker may not fire on every navigation if not configured.

Exactly how to do it:

1. Ensure your SPA uses `gtag(‘config’, ‘G-XXXXXXX’, {‘page_path’: newPath});` for each virtual pageview.
2. The linker needs to be triggered on outbound clicks – use GTM’s ‘Click – Just Links’ trigger instead of ‘All Pages’.
3. If your SPA uses pushState, you may need to programmatically add the `_gl` parameter to URLs that leave the app.
4. Use the `gtag(‘get’, ‘G-XXXXXXX’, ‘client_id’, callback)` to retrieve client ID and append it to outgoing links.
5. Test all user flows (e.g., ‘Add to cart’ → ‘Checkout’ on a different domain).

Pro script / template: “A Dhaka fintech app uses React SPA on one domain and a payment form on another. We used GTM’s Link Click trigger with a custom JavaScript that checks if the link goes to the payment domain. On click, we appended `_gl` parameter with the client ID from a cookie. This solved their broken funnels.”

📊 Expected results: SPA cross-domain tracking becomes reliable. Expect a 30% increase in reported conversions from SPA users.

Tactic 4.3: Periodic Maintenance and Audits

Why this works: Domains change, subdomains get added, and GA4 updates (like consent mode v2) can break cross-domain tracking without warning.

Exactly how to do it:

1. Every 3 months, review your cross-domain list against your actual domain architecture.
2. Check GA4 admin for any new referral exclusions that need updating.
3. Run a test flow (using DebugView) after any site redesign or migration.
4. Monitor GA4’s ‘User acquisition’ report for unexpected new user spikes – often a sign of broken tracking.
5. Use the free tool GA4 Audit Tool to check cross-domain settings.
6. If you change payment gateways or add a new subdomain, update the linker domains immediately.

Pro script / template: “We conduct quarterly GA4 health checks for all retainer clients. One client added a new blog subdomain (blog.fashionbd.com) but didn’t include it in cross-domain. Their blog traffic was appearing as separate users. A simple fix restored accuracy.”

📊 Expected results: Maintain data accuracy. Regular audits catch issues that could otherwise go unnoticed for months, saving ৳ thousands in wasted ad spend.

🏆 Real Case Study: How a Dhaka-Based Fashion Brand Recovered ৳6 Lakh in Attributed Revenue

Client: A mid-sized Dhaka fashion retailer (name anonymized as ‘StyleDhaka’) selling through their own website and a Shopify-based store (stylebd.com and shopify.stylebd.com).

Before: They were running Google Ads spending ৳12 lakh/month. Their GA4 reported 50,000 sessions/month, but they suspected under-reporting. Manual analysis showed users who browsed on stylebd.com and then purchased on shopify.stylebd.com were counted as two users. Their reported ROAS was 2.5x, but actual might be higher.

Strategy (we implemented):

• We audited their domain structure: main domain (stylebd.com), Shopify store (shopify.stylebd.com), payment gateway (pay.sslcommerz.com), and a blog (blog.stylebd.com).
• Set up cross-domain tracking in GTM: linked stylebd.com, shopify.stylebd.com, and blog.stylebd.com (note: payment gateway was third-party and couldn’t be fully tracked, but we added pay.sslcommerz.com as a referral exclusion).
• Configured self-referral exclusions for all owned domains.
• Fixed a bug where the Shopify site stripped `_gl` parameters due to a redirect.
• Added consent mode v2 for EU visitors.

Results after 3 months:

• Reported sessions increased by 35% (from 50,000 to 67,500) as previously fragmented sessions merged.
• Attributed revenue from cross-domain users rose by ৳6.2 lakh/month – previously invisible.
• Actual ROAS corrected to 3.4x (up from reported 2.5x).
• Retargeting lists grew 20%. They could now retarget users who visited the blog and later purchased on the main store.
• Time to goal improved: average session duration for cross-domain users was 8 minutes vs 3 minutes for single-domain users.

Client quote: “We never realized how much data we were losing. Rafirit Station’s team fixed our cross-domain tracking in just two days, and the impact on our reporting was immediate. We now see the true customer journey and can allocate budget more effectively.” – Marketing Head, StyleDhaka

See more Rafirit Station case studies →

✅ Cross-Domain Tracking Checklist

❓ Frequently Asked Questions

🎯 The Bottom Line

Cross-domain tracking in GA4 is not optional for businesses operating across multiple domains or subdomains. Without it, your data is incomplete and your attribution is broken. The setup is technical but manageable if you follow a systematic approach.

Here’s the counterintuitive insight: the biggest value from cross-domain tracking often comes from fixing attribution for high-value, long-funnel users – those who research on one domain and purchase on another. These users are your most profitable, yet they are the ones most often fragmented by missing cross-domain setup. By fixing this, you not only improve reporting accuracy but also enable better retargeting and lookalike audiences.

Don’t wait. Set up cross-domain tracking this week. If you need help, our team at Rafirit Station in Dhaka can do it for you in 48 hours. The cost of inaction is far greater than the investment.

⚡ Your Next Step (Do This Today)

1. Gather a list of all domains and subdomains your business uses.
2. Log into your GA4 property and check if any cross-domain settings exist.
3. Add your domains to the linker (GTM or gtag).
4. Set up self-referral exclusions in GA4 admin.
5. Test using DebugView and Real-Time reports – follow the checklist above.

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