Platform
Event routing
Every conversion becomes one clean event, passes the gates once, and then goes only to the platforms you choose, with duplicates removed. This is the clean-and-route step in the middle.
What it is
Event routing is how DataCops decides which of your connected ad platforms each event should go to. You set the rule per event and per platform, DataCops runs the event through the consent and fraud gates first, removes duplicates, and then delivers it to each destination you picked.One clean event
A conversion can come from many places: the pixel finding a form, a lead form, a Shopify order, a custom event you mapped, or a call to the API. Whatever the source, DataCops turns it into one clean event first: one event name, one time it happened, one stable ID, the person's matched identity and ad click, the consent answer, and the fraud verdict.
Only after that single, tidy version exists does anything decide where the event goes.
Gates first, then routing
The checks always run before routing, and they run once for the whole event, not once per platform. An event only reaches the routing step after it clears all of them, in order:
- Is your account active.
- Consent. In regions that require it, the person must have given a clear yes before anything moves.
- The fraud verdict. Verified human, or flagged. By default only verified events are sent.
- Duplicate check, so the same event is never counted twice.
- Match check, so each platform gets what it needs to recognise the event, like an ad click ID or a hashed email.
Then, and only then, the clean event is shaped into each platform's own format and delivered to each one on its own. If one platform is down or rate-limited, it never holds up the others.
You choose the destinations
Routing is set per event and per platform, and you control it. You might send Purchase to Google and Meta, but send Lead to LinkedIn only. Turning a platform off for one event does not change any other event. A new conversion starts out sending to all your connected platforms, and you can edit that at setup.
No double counting
Each clean event carries one stable ID that survives retries. For a purchase, that is tied to the order. Every platform uses that ID with its own duplicate check, so a resend or a replay is never counted twice. The ID is worked out once, in one place, and reused for every destination, so no platform ever sees a different version of the same event.
Hold a lead until it qualifies
Because delivery is server-side, DataCops can do something a browser tag cannot: hold a lead and only release it once it is confirmed. When your CRM or payment provider marks the lead as qualified or paid, DataCops releases it to your ad platforms as a conversion, with the original ad click still attached. That way your ads learn from real, qualified people, not from every raw form fill.