# Count each conversion once

How a conversion reported by your browser pixel, by Zernio and by your backend is counted once: one event id shared by every copy.

A purchase can reach an ad platform up to three times: from its browser pixel, from Zernio's tag and from your backend. One shared event id makes the platform keep only one.

## Why the same id matters

Each ad platform drops a conversion it already counted when the new copy carries the same event id. Two copies with different ids count as two sales.

The commonest cause of doubled purchases is a pixel and a server send that each made up their own id.

<DedupFlow />

## Share the id with your pixel

Pass your own id, such as the order id, to `zernio('track', …)` and to your pixel:

```js
zernio('track', 'Purchase', { eventId: 'order_1042', value: 129.99, currency: 'USD' });
fbq('track', 'Purchase', { value: 129.99, currency: 'USD' }, { eventID: 'order_1042' });
```

Without an `eventId`, Zernio makes one. Read it from the `zernio:event` event and give it to your pixel, as shown on [The tracking script](/products/server-side-tracking/script#use-the-event-id-in-your-pixel).

## Share the id with your backend

When your backend also sends the purchase to `POST /v1/events`, send the same `eventId` there. Each platform then keeps one copy of the three.

To keep a destination from receiving both copies at all, give its [forwarding rule](/products/server-side-tracking/ad-accounts#choose-with-the-api) one source: `web` or `api`.

## Stores count their own orders

On a store whose orders reach Zernio from the store itself (`storeOrders: true` on the site), the order is the record.

The website purchase is still sent to ad platforms, so they deduplicate it against the pixel, but it is not stored a second time.

## Which field each platform matches

| Platform | Matched on |
|---|---|
| Meta, TikTok, Pinterest | `event_id`, within 48 hours on Meta |
| Google Ads | The transaction id |
| Reddit | `conversion_id` |
| LinkedIn, OpenAI Ads | The event id |
| AppLovin | `dedupe_id` |

Zernio fills each one from the same event id. The full list is on [Platforms](/products/conversions-api/platforms#event-names-value-and-dedup).

## How it behaves

- **Event ids are per event.** Use one per purchase, not one per visitor or per page.
- **Ids are kept apart by site.** A website event is stored as `web:<siteId>:<eventId>`, so it never replaces an event your backend stored under the same id.

## Related

- [The tracking script](/products/server-side-tracking/script)
- [Send events](/products/conversions-api/send)
- [Test and verify](/products/server-side-tracking/verify)