Products
Event Manager
One list of every conversion you track, mapped in plain language, and shown per platform as delivered, held, skipped, or failed with the real reason. Configuration you can see, not tracking you have to trust blindly.
The problem
Conversion tracking is normally spread across three systems that were never designed to agree: a tag manager that fires events in the browser, a pixel that each ad platform gives you separately, and a CRM that holds the leads. Nothing shows you, in one place, what you are tracking, what it maps to on each platform, or whether it is actually arriving. You configure it blind, and you find out something broke from a drop in results, not from a warning.Why it is hard, technically
Three gaps make conversion tracking so unreliable, and each one hides a different failure.
- No shared definition. The tag manager, the pixel, and the CRM each hold their own copy of what an event is. A change in one does not reach the others, so they drift out of sync and start reporting different numbers for the same conversion.
- No feedback loop. A browser tag fires and forgets. It never hears back whether the platform accepted the event, rejected the row, or silently dropped it. So a conversion can be quietly failing for weeks and every dashboard still shows the tag as installed.
- The mapping is manual and easy to get wrong. Each platform expects a specific event name. A signup has to be reported as CompleteRegistration, a sale as Purchase, a cart click as AddToCart. Map it to the wrong one and the platform optimises for the wrong thing, and nothing tells you.
What it costs you
- Hours of setup spread across tools that do not talk to each other, repeated every time your site changes.
- Events that silently break and go uncounted until the loss is big enough to notice in revenue.
- No way to prove a conversion landed on Meta or Google, so every attribution argument comes down to guesses.
- Wrong mappings quietly training your ad platforms toward the wrong goal.
How DataCops solves it
The Event Manager is the one screen where you set up what DataCops captures and where it goes. It is one list of every conversion you track, no matter how it was captured, and it is configuration, not traffic: the Event Manager writes the definitions, and the DataCops script fires them. You pick what to capture, map it to a standard ad-platform event in plain language, and then watch, per event and per platform, whether it delivered. There is one definition, one place, and a real feedback loop.Each conversion in the list shows its name, how it was captured, what it sends as, like Purchase or Lead or CompleteRegistration, and its status. Open a row to set the mapping, the value rules, which platforms it routes to, and whether it is on.
Four ways to capture
You choose how each conversion is captured. Use as many as you need; they all land in the same list and deliver through the same clean pipeline.
| Mode | What it does |
|---|---|
| DataCops Pixel | Already on and capturing the forms and buttons on your site automatically. Nothing to set up. |
| Select manually | Open your live site inside DataCops and point at any form, button, or page to track it. No code, no selectors. |
| Build a form | Create a form hosted by DataCops that carries first-party identity, so every submission arrives already matched to a person. |
| SignupCops | Capture signups the browser pixel can never see, like Sign in with Google, where there is no form to submit. |
After a manual setup, DataCops shows a short confirmation of the trigger, the fields it captured, and what it sends as, so you can see the event is live before you leave the screen.
One definition, every destination
When you map an event once in the Event Manager, that single definition drives every platform. The captured conversion is turned into one clean event, already carrying the person's matched identity, their ad click, the consent answer, and the fraud verdict, and that one event is what fans out to each destination you chose. You are not maintaining a separate copy of the event for Google, for Meta, and for TikTok. You maintain one, and it is distributed everywhere.
That is why the numbers finally agree. Every platform is receiving the same event, resolved the same way, deduplicated so a retry is never double-counted.
See what delivered, and why
This is the feedback loop that browser tags never had. Open any event and you see its delivery status at a glance: delivered when everything went out, partial when some platforms failed, failed, held when it is waiting on a qualification step, or skipped.
Below that, one card per connected platform tells you the truth for that platform: sent, or skipped with a plain reason like "no ad click or email" or "consent not granted," or failed with the platform's own error, such as an expired ad click or a connection that needs reconnecting. It shows how long ago it was tried and which detail it matched on. A platform rejecting a single row is recorded as a failure, never as a false success. You stop guessing whether your tracking works, because the Event Manager tells you, per event, per platform.