The Meta Conversions API sends your purchases and leads to Meta from a server, so ad blockers and browser limits stop fewer of them. DataCops sets it up with one script and no developer, deduplicates every event with the Meta Pixel and adds the hashed customer details Meta matches on.
Every conversion, online and offline, checked before your ads learn from it
Trusted by agencies and brands running paid media
The Meta Conversions API, also called Facebook CAPI, is Meta's way to receive conversion events from a server instead of only from the Meta Pixel in the browser. A server event is not stopped by an ad blocker or a browser that blocks third-party scripts, so Meta sees more of the purchases, leads and sign-ups your Facebook and Instagram ads caused, and its delivery learns from them.
DataCops runs the Meta Conversions API for you. One first-party script on your own subdomain sees each event, and DataCops sends it to your Meta dataset from the server with the same event_id as the pixel, hashed customer details and the ad click it kept. The same connection also carries CRM sales from HighLevel, HubSpot or any CRM.
DataCops sends Meta Conversions API events from the server with one script, deduplicated with the Meta Pixel by event_id and matched with hashed customer data.
What reaches Meta
Meta optimizes on the conversions it receives. A browser pixel alone sends fewer of them, and some of them are not people.
Ad blockers and browser privacy settings stop the Meta Pixel for part of your visitors. Their purchases never reach Meta, so your ads look worse than they are.
Safari clears cookies set by a browser script after 7 days. A buyer who comes back later has no fbclid left to match to the ad.
Opportunity in your CRMFor lead businesses the real sale is a booked call or a won deal in the CRM, which the pixel never sees.
The pixel fires for bots too. Every fake lead tells Meta to find more people like it.
Four steps from the ad click to a matched server event, with no server container to host.
HighLevel Marketplace
Meta Sent once 
Google Ads Sent once 
TikTok Sent once 
LinkedIn Sent once Each event reaches Meta as it happens, well inside the 7-day limit.
The Meta Pixel sends the purchase from the browser. The Conversions API sends the same purchase from the server. Without a shared key, Meta counts two sales.
When the browser event and the server event have the same event name and the same event_id, Meta keeps one and drops the copy. DataCops puts the event_id on both.
When an ad blocker stops the pixel, only the server event arrives, and it is still counted. When both arrive, you still see one conversion.
Event Match Quality is the score from 0 to 10 that Meta shows in Events Manager for each server event. It rates how well the customer details you send let Meta find the person on Facebook or Instagram.
Email, phone, name and address fields are normalised and hashed with SHA-256 before they are sent, as Meta asks. Phone numbers are hashed as digits with the country code.
DataCops keeps the fbclid from the ad click on your own domain for up to 90 days and sends it as fbc, next to the browser ID, IP address and user agent.
Traffic Visibility
First-Party Script
Blockers and ITP cut your sessions
“15 minutes to get server-side tracking live. After 3 days failing with another app and a DIY server-side Google Tag Manager, that alone sold me. Then support jumped on a Google Meet with me on a Sunday afternoon to finish the job. Nothing else comes close.”
Meta shut down its separate Offline Conversions API and offline event sets in May 2025. Offline and CRM sales now go through the same Conversions API as website events, into a dataset.
Meta turns away events sent more than 7 days after they happened. A monthly or weekly CSV of won deals loses its oldest rows, so each stage should go out on the day it happens.
Meta matches an offline sale to a person by hashed email and phone, and by the click ID when there is one. The more of these you send, the more sales Meta can credit to an ad.
Install once for the agency and pick sub-accounts. DataCops sends the form or survey lead, the booking, the show-up, the won deal with its value and the paid invoice. Cancellations, no-shows and lost deals are never sent.
Pick the lifecycle stage that means qualified. DataCops checks HubSpot every 5 minutes and releases the held lead to Meta when it gets there. Held leads expire after 14 days.
Salesforce, Pipedrive or anything else posts a sale to your private webhook, directly or through Zapier, Make or n8n. Read the full guide on Meta offline conversions.
Events Manager shows what arrived. DataCops also shows what was held back, and why.
Checked September 2026 against each option's own documentation.
Better to know now than after you connect.
Read the score in Meta Events Manager. DataCops shows what it sent for each event and what it matched on.
Bot filtering for Meta starts off on a new site. Turn it on from day one.
Checkout purchases, Shopify orders and won stages from your CRM are sent today.
Meta offers no way to take back a purchase once sent. Google Ads refunds are corrected.
About 5 minutes per site. Agencies: about 15 minutes per client.
Add the DataCops script
One script and one DNS record, so events and ad clicks are seen on your own domain.
Connect Meta
One-click sign-in to your Meta ad account and dataset. Keep your pixel running.
Pick events and sources
Choose the website events to send, and connect HighLevel, HubSpot or a webhook for later stages.
DataCops is a tool that sends Meta Conversions API events from the server with one script, deduplicated with the Meta Pixel by event_id and matched with hashed customer data, plus the sales that close after the click, with a log of every send.
One script and one DNS record collect on your own subdomain, so there is no Google Tag Manager container to build. With your DNS on Cloudflare, the free Worker reads the click ID at the edge before the page loads. A missing fbc is built from the kept fbclid, click IDs are kept for up to 90 days, and a signed server-set cookie lasts up to 400 days where enabled.
DataCops passes an event_id with every server event. Meta keeps one event when the browser and server events share the same event name and event_id, so a purchase is not counted twice.
Email, phone, first and last name, city, state, postcode, country, gender and date of birth are SHA-256 hashed, with client IP address, user agent, fbc, fbp and external ID sent alongside. Meta shows the Event Match Quality score in Events Manager.
A declined or rejected consent choice skips the send, and California visitors are sent with Limited Data Use. The first-party consent manager, built on IAB TCF v2.2, is served from your own domain. First-party analytics, a GA4 alternative, shows the same traffic.
HighLevel natively (lead, booked, showed, won with value, paid), HubSpot through one stage, any CRM by webhook, Shopify through the DataCops Shopify app. Meta rejects a request with any event older than 7 days, so each stage is sent when it happens. See Meta offline conversions.
Every visit gets a bot verdict against 360+ billion IPs, with a per-platform Real people only switch (off by default), and every form email is checked for disposable providers, domains with no mail server and an email risk score. Ads Warmup sends up to 20,000 past customers, dated when you send. A delivery log row shows each send as sent, held, skipped or failed.
Best for: advertisers on Meta who want server-side events without building a container: ecommerce, lead gen, clinics, home services, B2B and agencies.
Free to start. See pricing.
A single store with basic needs may be fine on Meta's own Conversions API setup in Events Manager or its Shopify integration.
DataCops is not a Google Tag Manager container. Keep a server-side container if you need custom tags, or GA4 and BigQuery feeds.
Event Match Quality is shown by Meta in Events Manager, not inside DataCops.
Refunds and cancellations do not reach Meta. See what happens to a refunded sale.
Platform rules checked October 2026. Rules change; check the platform's own page before you build.
The Meta Conversions API (CAPI) is the way to send conversion events to Meta from a server instead of only from the Meta Pixel in the browser. Ad blockers and browser privacy limits cannot stop a server event, so Facebook and Instagram ads see more of the purchases and leads they caused.
Server-side events, counted once, matched on hashed data, logged per send.
Setup in 5 minutes. No credit card.
Live traffic quality
Visits · last 24h
Without filtering, 26.5% of your reported traffic is bot noise inflating dashboards and draining ad spend.
Make confident, data-driven decisions with
actionable ad spend insights.
© 2026 DataCops. All rights reserved.
