Platform
Conversion data quality
Every conversion you send is a lesson for the ad platform. Teach it with bots and it finds more bots. Teach it with real buyers and it finds more of them.
The idea
A conversion you send to Meta or Google is not just a number in a report. It is training data. The platform already knows a lot about the person who clicked your ad. The moment you report that they converted, its algorithm decides that people like them are worth finding, and spends more of your budget going to find them.So the quality of what you send decides the quality of who the algorithm targets next.
It cuts both ways
Feed the algorithm junk, a bot or a fake form fill, and you are not just messing up a dashboard. You are teaching it to go find more of the same. You then pay real money to bring in more non-human traffic while the dashboard looks healthy.
One accurate, verified, qualified lead teaches the algorithm more than a hundred noisy form submissions, because the hundred are mixed with junk and the one is pure signal. Many advertisers optimise for how fast a conversion is reported, not how good it is, and then wonder why campaigns drift toward cheap, low-quality traffic.
The five parts of a good conversion
DataCops works on each part before a conversion leaves its servers:
| Part | The question | What DataCops does |
|---|---|---|
| Real | Was it a person? | Bot verdict on every session, and Real people only per platform. |
| Matched | Can the platform tie it to an ad click? | Keeps click IDs, sends normalized and hashed email, phone and name. |
| Once | Is it counted one time? | One sale per order ID and one lead per email, per platform. |
| Qualified | Did it matter to the business? | Holds leads until your CRM confirms them. |
| Allowed | Did the person consent? | Checks consent on the server before every send. |
Keep bots out
Every session gets a human or bot verdict with reasons, from headless browsers like Puppeteer and Playwright to automation signs in the browser. Every visitor IP is checked against DataCops' own IP intelligence for datacenter, VPN, proxy and Tor. Those flags ride along with each conversion.
Then you decide what each ad platform receives. By default DataCops sends everything and the verdict travels as information. Switch on Real people only for a platform and DataCops stops conversions that match the tiers you tick:
| Tier | Default when switched on |
|---|---|
| Bots | On |
| Datacenter IP | On |
| Proxy, VPN or Tor | Off (many real B2B buyers use a work VPN) |
| No user agent | Off |
Stopped conversions show in the delivery report as "Visitor looked fraudulent". See Real people only and Bot and fraud detection.
Help the platform match
A conversion the platform cannot match to a person teaches it nothing. DataCops keeps the ad click ID with each visitor, links an email when the visitor shares one, and sends cleaned customer details: email, phone, names, city, region, zip and country, normalized and SHA-256 hashed right before sending. For Meta it also sends fbc, fbp, IP, user agent and an external ID.
For uploads and Ads Warmup, DataCops shows a match score out of 10 per person: email 3, phone 2, first and last name 1.5, ad click ID 1.5, country 1, city or zip 1, external ID 1. It is our own estimate to guide you, not the platform's official score.
Count each sale once
The same order can arrive from the browser, from Shopify and from a webhook. DataCops sends one Purchase per order ID per ad platform, and one Lead per email per platform within 30 minutes. Repeats are logged as duplicates, not sent. See Conversion deduplication.
Count leads once qualified
DataCops follows a strict order so the platform learns from people who matter:
Count every real lead
With its ad click attached, so the algorithm learns from real people.
Keep fraud and junk out
With Real people only and SignupCops holding fake sign-ups.
Send high-value leads once qualified
Once sales accepts them, so the algorithm optimises toward revenue, not toward "someone filled out a form."
For the third step, set the event to hold. HubSpot is checked every five minutes for the field and value you choose, or your system calls the release API, or you mark the lead in the dashboard. The lead then goes out with its original click. Held leads expire after 14 days. See Qualification gate.
Keep values honest
Purchase values flow through when your site, store or API call sends them, so value-based bidding sees what was really paid. When a sale is refunded, DataCops corrects it in Google Ads: a full refund retracts the conversion and a partial refund lowers its value. Meta and TikTok do not offer a correction call.
Health businesses can switch on health mode, which sends ad platforms only the click, the value and the homepage address, with no page paths or treatment names. See Meta health and wellness restrictions.
Why a tag manager cannot do this
A tag manager, in the browser or on a server, fires the instant a form is submitted. It cannot hold a conversion for days while it waits to see if the lead is real. The usual workaround, syncing the lead to a CRM and firing to Meta when it is marked qualified, breaks at every joint: the ad click gets lost on the way to the CRM, and the systems were never built to talk across a multi-day timeline.
DataCops closes that gap. Delivery is server-side, so it can hold a lead and release it later with the original ad click. Every event passes the consent and duplicate checks once, then goes to each platform you picked: Meta, Google Ads, TikTok, LinkedIn, Microsoft Ads, Reddit, Pinterest and X. And there is a clear record of what was sent, held or skipped.