Products
CAPI delivery
Clean, verified conversions sent to every ad platform from the server, matched properly, never counted twice, and logged so you can see them. They arrive when the browser would have blocked them, and they match better when they do.
The problem
The way most conversions reach an ad platform is a pixel firing in the browser. That is exactly where tracking is weakest. Ad blockers strip the pixel, Safari and iOS limit it, and a visitor who rejects cookies removes it. So a large share of your real conversions never leave the browser, and the ones that do often arrive with thin match data, just a cookie, no strong identifier, so the platform cannot confidently tie the conversion to the person who clicked the ad.Why browser delivery fails
A browser pixel is the wrong place to report a conversion, for three technical reasons.
- It runs in a hostile environment. The pixel is third-party code in a browser that is actively trying to block third-party code. Blockers, tracking protection, and consent rejection all remove it before it can send, and none of them tell you it was removed.
- It carries weak identity. Even when a browser pixel does fire, it usually has only a browser cookie to offer. Ad platforms match far better on the ad click ID and on hashed, verified customer details, which a fragile client-side pixel rarely assembles reliably.
- It fires and forgets. The pixel sends into the void. It never learns whether the platform accepted the event, rejected the row, or dropped it. A conversion path can be broken for weeks while every dashboard shows the tag as installed.
What it costs you
- Your ad platforms bid on incomplete data, so they find fewer of the right people and your cost per real conversion rises.
- Winning campaigns look weak because their conversions went missing, so you cut budget that was actually working.
- Low match quality means the platform cannot connect many conversions to a click at all, so your attribution and your optimisation both degrade.
- You cannot reconcile what your ads report with what actually happened in your store or CRM.
How DataCops solves it
CAPI delivery sends conversions to your ad platforms server to server, the way the platforms themselves recommend. CAPI stands for Conversions API. Instead of hoping a browser pixel survives, DataCops delivers each conversion from the server as one clean, fully resolved event, so it arrives even when the browser would have blocked it, and it arrives with strong match data attached. Connect each ad account once, and every clean, consented event is delivered to all of them.The difference is not just where the event is sent from. It is what is sent. A DataCops conversion is not a bare pixel firing. It is a complete, verified record of a real person.
One clean event
Every conversion, whatever its source, is first turned into one clean event before any platform sees it. That event carries:
- The event name, the real time it happened, a stable ID, and the value and currency, never a fabricated zero.
- The person's first-party and edge-captured ad click, kept exactly as each platform expects it.
- Their customer details, normalised and securely hashed once, so the platform can match on email or phone without ever receiving raw data.
- The resolved consent answer and the fraud verdict.
And if the visitor converted anonymously today but identified themselves on an earlier visit, DataCops finds that stored identity, held on its 400-day durable identity, and attaches it before delivery. So a conversion that a browser pixel would have sent with nothing to match on goes out with a real, verified identity behind it.
The gates
Before anything is sent, the one clean event passes the same checks, once, for the whole event:
- Your account is active.
- Consent is in place where it is required. See the consent manager.
- The fraud verdict is clean. By default only verified events are sent. See bot and fraud detection.
- The event is not a duplicate.
- It has the minimum a platform needs to be matched, like an ad click or a hashed email.
Sent to each platform, counted once
The one clean event is put into each platform's own format and sent to each of them on its own. If one platform is down or busy, DataCops keeps trying it while the others still go through, so a problem with one never holds up the rest. Each platform is only sent conversions that are still inside the time window it will accept.
The same conversion is never counted twice. If the same order comes in more than once, say a store that sends it twice, DataCops catches the repeat before anything goes out. And every event carries one steady ID that each platform also uses to spot a repeat on its side. So you can even keep your old pixel running next to DataCops without your numbers doubling up.
Supported destinations
DataCops delivers to the major ad platforms and can sync to HubSpot, each with the match key it needs:
| Destination | Matched with |
|---|---|
| Google Ads | gclid, wbraid, gbraid |
| Meta | fbclid, plus hashed email or phone |
| TikTok | ttclid |
| li_fat_id, plus hashed email | |
| epik | |
| rdt_cid | |
| HubSpot | contact and conversion sync |
You connect each account once, usually with a single login, and choose per event which destinations it goes to.
See what was sent, and why
This is the feedback loop a browser pixel never had. Every attempt is recorded, one record per event per platform: sent, skipped, or failed. A platform rejecting a single row is recorded as a failure, never as a false success, and the platform's own words are shown, like an expired ad click or a connection that needs reconnecting. It shows how long ago it was tried and which detail it matched on. So you can see, per event and per platform, exactly what delivered and why, instead of trusting that a tag is still working.
Why it outperforms
Server-side delivery does not just recover lost conversions, though it does that. It also makes the conversions you send worth more to the algorithm:
- Higher match quality. Because each event carries the ad click plus hashed, verified customer details, the platform can confidently connect it to the person who clicked. Stronger matches mean the platform learns more from each conversion.
- Recovered volume. The conversions that ad blockers and Safari used to hide are now delivered, so the platform is optimising on your whole audience, not a fraction.
- Clean signal. Only verified, consented conversions go out, each counted once, so the algorithm is trained on real buyers instead of bots and noise. Clean data in, better targeting out.
More conversions, better matched, all real. That is why a verified server-side conversion outperforms a browser pixel firing into the void.