Platform reconciliation · Verification tier

Your numbers, checked against theirs.

Every hour TracerKit compares what it observed on your site with what Meta and PostHog report, and flags drift over 20% so you can fix it.

the problem

Why this breaks today.

✗

Platforms disagree, and nobody knows who's right.

Meta says one number, your analytics another, your store a third. Without a reference count you can't tell a tracking bug from attribution noise.

✗

Breakage looks like performance.

A tracking gap shows up as a worse campaign. Teams cut budgets on campaigns that were fine and blame creative for a broken pixel.

how it works

How TracerKit handles it.

✓

An observed count of your own.

TracerKit counts the events it saw fire on your site, per metric, so there is a neutral number to compare against.

✓

Hourly comparison against the platforms.

Using read access you connect, TracerKit pulls what Meta and PostHog report for the same window and computes the drift.

✓

Alerts past your threshold.

Drift beyond 20% on a big-enough sample opens an alert. A healthy reading resolves it.

questions

Asked and answered.

Which platforms can I reconcile against?+

Meta and PostHog today. Meta's insights are daily-grained, so Meta drift is measured per day; PostHog is measured per hour.

Will the numbers ever match exactly?+

Rarely. Ad blockers, consent and attribution windows all create some gap. Reconciliation is about catching a gap that changes, which is what a broken tag looks like.

Do I need to give TracerKit write access?+

No. Reconciliation only reads reported counts.

the terms behind it

more of what you get

Stop guessing whether your tracking works.

Tag management is free forever. Paid tiers start with a 14-day trial, no card.