Sample tracking beacon audit report

An anonymized sample tracking audit report: per-URL beacon rows with extracted IDs, the findings they led to, and what was fixed.

Illustrative sample. The company, domain, and every identifier below are fictional and anonymized — this is what a finished beacon report looks like, not a real site's data.

The audited site (fictional)

Northwind Traders, a fictional mid-size B2B software company at shop.northwind.example — marketing site plus docs, blog, and a signup flow, ~1,300 pages. Static scan plus browser-render pass.

Report summary

• 1,284 pages audited (200 OK)
• 312 pages carrying at least one tracker
• 14 distinct trackers found; 9 with extracted IDs

Beacon findings (excerpt)

Tracker	Type	Identifier	Where	Finding
Google Tag Manager	Container	GTM-XXXX12	All pages	Single container — good
Google Analytics 4	Analytics	G-XXXXXXX12	All pages	Primary property
Google Analytics 4	Analytics	G-XXXXXXX34	Blog only	Duplicate — old blog property double-counts
Meta Pixel	Advertising	100000000000001	All pages	Fires pre-consent — see consent sample
LinkedIn Insight Tag	Advertising	200001	Landing pages	Intended
Hotjar	Session replay	3000001	Pricing, signup	Intended
Unknown pixel	Advertising	400000000000002	3 legacy landing pages	Unrecognized — no owner found
Universal Analytics	Analytics	UA-000000-1	Docs template	Orphaned — dead since 2024

What the findings led to

1. Removed the duplicate GA4 property from the blog template — attribution was double-counting every blog conversion.
2. Killed the unknown pixel after no team or vendor dashboard claimed its ID; it had been firing on three old landing pages for years.
3. Deleted the orphaned UA tag from the docs template — it collected nothing and hadn't been looked at since the GA4 migration.
4. Moved the Meta Pixel behind the consent gate — it was hardcoded in the base template and fired before visitors consented.

Re-audit after the cleanup: 10 trackers, zero duplicates, zero unknowns. The safe removal method · the full audit method.