QA finding
Sections of the site report to different analytics accounts, or to none that is connected
QA Warning Severity: Medium
Part of the audit Analytics and the crawl see different sites. Finding id: qa.trackingIdsDiffer.
What it costs you
Visits are split over accounts, so no report shows the whole site, and a journey that crosses sections is counted as two visitors.
What to do
Decide which account the site reports to and use its id on every page.
What it checks
- Different tracking IDs in different sections
- Tracking tag present but no data
How to fix it
Find where the tag reports to
- Open an example page with the network panel open and filter on the vendor's host.
- If no request is sent, the tag does not fire: check its trigger and the consent setting.
- If a request is sent, read the id in it and find who owns that account.
How to check: The pages show sessions in the connected property, or the finding is dismissed because the other account is meant.
Report to one account
- List the ids in the finding with the sections they are on.
- Ask who owns each account. An id nobody claims is often left from an agency or an old site.
- Replace the ids you do not keep with the one you do, in the template or the tag manager container of that section.
How to check: Crawl the site again. One id is left per vendor.
Thresholds
| Name | Default | Meaning |
|---|---|---|
min_pages | 5 | A tag id on fewer pages than this is not returned as 'no data'. |
How to verify by hand
Analytics landing pages and Search Console pages.
What this relies on
A page with visits exists and matters, even when no link leads to it. One site is expected to report to one account.