How do we fix broken tracking?
Fixing broken tracking starts with a pixel audit and usually ends with a server-side implementation — because most 'broken' tracking isn't broken, it's blocked. Safari's ITP caps client-side cookies at as little as 24 hours to 7 days, ad blockers strip pixels for a meaningful share of users, and consent rejection removes 20–40% of events in strict regions. Client-side-only tracking is a structurally failing strategy in 2026.
Key facts
- Safari ITP limits many client-side cookies to 24 hours–7 days, breaking attribution for any consideration cycle longer than a week.
- Server-side tracking (Meta CAPI, GA4 Measurement Protocol) typically recovers a double-digit percentage of conversions lost to browser blocking.
- The audit order: verify events fire (tag debugger), verify they arrive (platform diagnostics), verify they match reality (CRM reconciliation).
Why tracking degrades even when nobody touched it
Browser updates (ITP, ETP), consent-mode changes, iOS releases, and platform migrations continuously erode client-side tracking without any change on your side. A setup that measured 90% of conversions two years ago may capture 60% today — and the decline is silent.
What broken tracking costs
You are flying blind: automated bidding optimizes on incomplete data, budget flows toward whatever still happens to be measurable, and 'underperforming' channels may simply be under-measured ones. Optimization decisions made on 60% visibility are guesses wearing a dashboard.
The repair sequence
First, audit: use tag debuggers to confirm every conversion event fires on the correct action, and platform diagnostics to confirm receipt. Second, fix the GTM container — orphaned tags, duplicate fires, missing triggers are endemic. Third, implement server-side tracking so events flow from your server to platforms, bypassing browser blocking. Fourth, reconcile against CRM data monthly to catch future drift.
When to bring in a specialist
Server-side implementation is genuinely technical — CAPI deduplication, event matching quality, consent-mode configuration. A tag development specialist (this is core Media Ops Machine work) typically completes what an internal generalist team would spend months debugging.
Frequently asked questions
Why did our tracking break when nobody changed anything?
Browsers changed it for you. Safari ITP, ad blockers, and consent enforcement continuously erode client-side pixels — setups silently drop from ~90% to ~60% conversion capture over a couple of years.
What is server-side tracking?
Sending conversion events from your server directly to ad platforms (Meta CAPI, GA4 Measurement Protocol) instead of relying on browser pixels — bypassing blockers and recovering a double-digit share of lost conversions.
How do we know if our tracking is broken?
Reconcile platform-reported conversions against CRM or transaction records monthly. Gaps beyond the normal 20–30% attribution variance — or sudden shifts — indicate tracking failure, not performance change.