Search Atlas Help Center

🔍 Fix GA4 Cross-Site Tracking Data in Single Property

Open in
View as Markdown Open in ChatGPT Open in Claude
Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

🧩 What Is This Issue?

Some customers have noticed unexpected cross-site tracking data appearing inside a single Google Analytics 4 (GA4) property. For example, data from one domain showing up under a property that should only track a different domain. This can distort your traffic reports, inflate session counts, and make it harder to analyse accurate SEO performance.

This article explains the most common causes of this issue and walks you through how to diagnose and fix it — including how Search Atlas connects to your GA4 data.

🔎 Does Search Atlas Cause This?

Search Atlas reads your GA4 data using a secure, read-only integration. It does not inject tracking scripts, modify your GA4 configuration, or send data into your GA4 property. If cross-site data started appearing in your GA4 property around the time you connected Search Atlas, the root cause is almost always a pre-existing configuration issue in GA4 that becomes more visible once you start actively reviewing your analytics.

⚠️ Common Causes of Cross-Site Data Contamination

  • Shared Measurement ID: The same GA4 Measurement ID is used on more than one domain or subdomain, causing all traffic to roll up into one property.
  • Cross-Domain Tracking misconfiguration: GA4 cross-domain tracking is enabled but the domain list includes domains that should be tracked separately.
  • Third-party embeds or iframes: Widgets, booking engines, or payment portals hosted on another domain that carry your GA4 tag.
  • Tag Manager container errors: A Google Tag Manager container is firing your GA4 tag on unintended domains due to a missing or incorrect trigger filter.
  • Referral exclusion settings: Missing referral exclusions can cause sessions to restart mid-journey and attribute traffic incorrectly.

🛠️ How to Diagnose the Problem

  1. Open your GA4 property and navigate to Reports → Acquisition → Traffic Acquisition.
  2. Add a secondary dimension of Hostname to see which domains are sending data into this property.
  3. If you see hostnames that do not belong to this property, you have confirmed cross-site contamination.
  4. Note the hostnames and the date the unexpected data first appeared — this helps narrow down what changed.

✅ How to Fix Cross-Site Data in GA4

Once you have identified the unexpected hostnames, follow the steps below based on the most likely cause.

Fix 1 — Remove unintended domains from Cross-Domain Tracking:

  1. In GA4, go to Admin → Data Streams → select your web stream.
  2. Click Configure tag settings → Configure your domains.
  3. Review the domain list and remove any domains that should not be sharing session data with this property.

Fix 2 — Add hostname filters to your Data Stream:

  1. In GA4, go to Admin → Data Streams → select your web stream → Configure tag settings.
  2. Use the List unwanted referrals and internal traffic settings to exclude domains sending unwanted hits.

Fix 3 — Fix your Google Tag Manager trigger:

  1. Open your GTM container and locate the GA4 Configuration tag.
  2. Edit the trigger and add a condition: Page Hostname → equals → your intended domain only.
  3. Publish the updated container.

Fix 4 — Create a filtered GA4 property (recommended for clean reporting):

  1. In GA4, go to Admin → Data Settings → Data Filters.
  2. Create a new filter using the Hostname dimension to include only your intended domain.

📊 Verifying Your Search Atlas Integration

To confirm your Search Atlas connection is working correctly with your clean GA4 data, navigate to Site Metrics (Site Explorer) in the left sidebar of the platform. Your traffic and keyword data should reflect only the property you have connected. If you connected multiple properties, verify each one under Keywords → Rank Tracker to ensure the correct domain is selected.

🚀 Preventing This Issue in the Future

  • Always use a separate GA4 property for each distinct domain — avoid sharing Measurement IDs across sites.
  • Audit your GTM container triggers whenever a new third-party tool is added to your site.
  • Review your GA4 hostname report monthly to catch unexpected data sources early.
  • Document which Measurement ID belongs to which property before connecting any analytics integration.

💬 Still Need Help?

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.