# When numbers don't match

Why your backend, Zernio and each ad platform count different conversions, which gaps you can fix, and which are expected.

Three systems count your conversions: your backend, Zernio and each ad platform. Their numbers never match exactly. Some gaps are a setup problem you can fix, others are how platforms count.

## Find where the gap is

Compare the three counts for the same days, then read the step where they split:

1. **Backend to Zernio.** `GET /v1/events?profileId=…&source=…` lists what Zernio stored. A sale missing here never arrived.
2. **Zernio to the platform.** [`GET /v1/events/accuracy`](/conversions/get-events-accuracy) shows, per destination, what was sent, accepted and failed.
3. **One event.** [Get one event](/conversions/get-event) shows each send with the platform's answer.

## Gaps you can fix

| What you see | Cause | Fix |
|---|---|---|
| Sales missing in Zernio | The tag is not on the checkout's thank-you page, or the backend call failed | [Verify the tag](/products/server-side-tracking/verify), and retry backend calls on a `5xx` |
| Stored, but `notSent` in accuracy | The visitor refused ad cookies, the event had no identifier, or the rule's `eventNames` left it out | Send `email` or a click id, and check the rule's event names |
| `failed` sends | The ad account lost access, or the platform refused the event | Read the error in [Get one event](/conversions/get-event), reconnect if asked |
| Too many conversions on the platform | The pixel and Zernio sent one sale under two ids | Send the same `eventId` from both. See [Deduplication](/products/server-side-tracking/deduplication) |
| Too many conversions in GA4 | GA4 counts every copy | Send each event to GA4 once, from one place |
| Events refused as too old | The platform's window passed | Send within 72 hours to GA4, 7 days to Reddit and Snapchat, 90 days after the click to Microsoft and X |
| Events in the wrong year | `eventTime` sent in milliseconds | Send Unix seconds |
| Nothing on the platform after a test | `testCode` was set, so the platform only validated | Drop `testCode` for live events |
| A sale counted in totals, not for a campaign | No click id or UTM tag reached Zernio | Send the visitor id from the tag, or the click id |

## Gaps that are expected

| What you see | Why |
|---|---|
| The platform reports more | It adds view-through and modeled conversions, which no server sends |
| The platform reports a sale on another day | It dates conversions by the ad click, Zernio by the event |
| Campaign totals differ | Each platform has its own attribution window. Zernio counts under the [model you choose](/guides/campaign-results#choose-an-attribution-model) |
| Match quality under 100% | Some visitors leave no email or click id |
| The newest hours are missing | Meta shows server events in about 20 minutes, Google Ads in a few hours |
| Days split differently | Zernio's overview and link stats use UTC days, ad platforms the ad account's timezone |

A gap of a few percent between Zernio and a platform is normal. Read `accuracy` in `GET /v1/events/accuracy`: under 95% of sales accepted means something to fix.

## How it behaves

- **Accuracy compares sales only.** It counts store orders and Stripe payments. Profiles that send through the API read `deliveries` instead.
- **Late matches.** An event with no campaign yet is matched again every hour for 7 days.
- **Alerts.** A destination whose accuracy falls under 95% sends an alert, at most once a day.

## Related

- [Choose how to send conversions](/products/conversions-api/choose)
- [Platforms](/products/conversions-api/platforms): what each platform gets and refuses
- [Test and verify](/products/server-side-tracking/verify)
- [Deduplication](/products/server-side-tracking/deduplication)