Warning Tracking & Analytics
Different GA4 ID than the rest of the site
- Severity
- Warning
- Impact
- Medium
- Effort to fix
- Low
- Issue code
track_inconsistent_ids
Why it matters
This page reports to a different GA4 property, so its visits are missing from the main reports.
How to fix it
Use the site's main GA4 ID here, or confirm the second property is intended.
What this means
This page sends data to a different GA4 property than most of the site. The evidence shows both, for example Uses G-OLD111; most pages use G-NEW222.
Why it matters
Visits to this page land in a different property, so the main property is missing them. Journeys that pass through the page are split across two properties, and conversions on it may be counted where nobody looks.
Common causes
- A separate template with an old or hard-coded measurement ID.
- A section on another system: a blog, shop or help centre with its own analytics settings.
- A staging or test ID published to some pages.
- A migration where some templates were updated and others were missed.
Sometimes it is intentional, such as a sub-brand with its own property. Then the question is whether the main property should receive the data too.
How to fix it
- Check which property each ID belongs to in GA4 under Admin > Data streams.
- Update the template or system serving this page to use the main measurement ID, or the main GTM container.
- If the section needs its own property, send to both from one place, so the main property stays complete.
Verify the fix
Recrawl. Improve > Tracking & Pixels shows which IDs each page uses. See also Analytics tag missing on this page.
How it affects your score
Tracking issues have their own Tracking score and never lower the SEO site health score. They still appear in the Action Plan, the issues CSV, Slack messages and Linear tickets. Weakens rankings, crawling or measurement. Fix after critical issues.
Find the affected URLs
Open Crawl > Issues and pick Different GA4 ID than the rest of the site. Each affected URL is listed with its evidence, and Copy URLs or Export URLs hands the list to a developer. The issue also appears in the Action Plan, ranked by impact (medium) and effort (low), and in the issues CSV under the code track_inconsistent_ids. After fixing, run a new audit and use Compare to confirm the URLs moved to fixed.
Guides that cover this issue
Related Tracking & Analytics issues
- CriticalGA4 sent by page code and by GTM
- CriticalGTM container not published or wrong ID
- CriticalPage view sent twice on one page load
- CriticalPersonal data or tokens in URL
- CriticalPixel initialised twice on the page
- CriticalTag loaded twice on the page
- CriticalTracking before consent
- WarningAnalytics tag missing on this page