What breaks Meta tracking
Meta tracking fails in boring ways: event names drift, parameters change, firing stops on certain pages, or browser conditions change. You usually find out after performance shifts.
What Kickin monitors for Meta
Especially purchase — the event that matters most.
Value, currency, content IDs changing unexpectedly.
Meta vs GA4 vs Google Ads counts diverging.
To Meta Conversions API (paid plans).
"What do I do now?"
Kickin creates an incident with the relevant context — what fired, what didn't, and when — so you can debug without guessing.
Why ad blockers and ITP matter
Browser restrictions are reshaping what's possible with client-side tracking. Here's what's actually happening:
Block Meta's pixel script entirely. No code runs, no events fire. This affects 15-30% of users depending on your audience and geography.
Caps first-party cookies at 7 days (or 24 hours in some cases). Returning visitors lose attribution context, making multi-touch attribution unreliable.
Firefox ETP, Brave, and incognito modes add additional restrictions. Each browser handles tracking differently, fragmenting your data.
What Kickin can (and can't) do about blocked users
What we can do
- ✓Detect when pixel events aren't reaching Meta (even if they fire client-side)
- ✓Send events server-side via Conversions API to bypass client restrictions
- ✓Show you the gap between expected and observed events
- ✓Dedupe server + client events automatically
What we can't do
- ✕Track users who block all JavaScript (very rare)
- ✕Restore cookie identity after ITP expires it
- ✕Override browser privacy settings
- ✕Guarantee 100% coverage (no one can)
See also: Meta CAPI deduplication, Server-side tracking
FAQ