Meta Conversions API Gateway: what it fixes, what it leaves

Live, green, and still incomplete

The usual story: a developer spends an afternoon provisioning the Gateway, Events Manager turns green, and the team considers tracking solved. Then a month later the leads that turn into customers still never reach Meta, and nobody can say how many of the "conversions" were real people.

The Gateway did its job. Its job is delivery. The questions it cannot answer are about what is being delivered.

A Gateway makes the pipe reliable. It does not look inside it.

The real cost of a cheap tool

Cheap tracking that is handled badly costs far more, because the bill arrives in what your ads learn.

• Bots forwarded as buyers. A forwarder sends what reaches it. Junk conversions teach the platform to find more junk.
• The sale that never gets sent. A booked call, a phone order or a won deal happens outside the store or the page. Most tools never see it.
• The limit you hit on your busiest day. Hosts and apps cap requests, events or orders, and sending can pause or stop over the limit.
• The build and the upkeep. Containers, plugins and automations need someone to build them and fix them when a platform changes.

The tracking is 0.17 percent of your spend. If one in five of the conversions your ads learn from is a bot or a fake lead, a fifth of the learning signal points at the wrong people, across the other 99.83 percent of the budget.

Cheap tracking is the cheapest line on the bill and the most expensive one to get wrong.

Ways to send Meta conversions

When not to use DataCops

• You want the Gateway's own cloud deployment. If your team wants Meta's Gateway or a container it controls, keep it. DataCops is a script, not a container.
• Your whole stack is Meta only and you have an engineer. The Gateway is free software and may be enough.
• You want a reporting dashboard. DataCops fixes what goes into your ads.

Ads Warmup: tell the ads who pays

Meta Conversions API Gateway forwards what your site or store produces. A new ad account, pixel or campaign has nothing yet, so it pays to learn from scratch. That is a job a pipe cannot do, because the customers you already have never visit on command.

Ads Warmup, DataCops' flagship feature, sends them to your ad platforms before a campaign spends:

1. Upload a customer list. A CSV of past buyers, old leads or booked calls. DataCops reads your columns; only email is required.
2. See a match score for every person. An estimate from 0 to 10 from email, phone, name, location, click ID and customer ID, before anything is sent.
3. Pick the event. Purchase, Lead, Complete registration, Add to cart or Schedule.
4. Send server-side. Up to 20,000 people per upload to Meta, Google Ads and TikTok, with a sent, skipped or failed result per person. Google Ads credits only people who clicked a Google ad.

Each row is dated when you press send, not with the old sale date, so it gives a new campaign real customers to learn from on day one. Preview is free; sending needs a paid plan.

What else a pipe never does

• Capture at the edge. With DNS on Cloudflare, the free, optional DataCops Cloudflare Worker reads click IDs and UTMs off the first request, before the page or any script runs. It captures; it does not block.
• Keep the click on the server. gclid, wbraid, gbraid, fbclid, ttclid and li_fat_id are stored for up to 90 days, so a deal that closes weeks later still finds its click. A signed server-set cookie lasts up to 400 days where enabled.
• Check the lead's email. Fixed rules, not guesses: disposable providers, domains with no mail server and an email risk score. With LeadCops (Business and up), a lead that fails is held and never billed.
• Install on Shopify. The DataCops Shopify app adds a web pixel and a theme app embed, so every paid order reaches your ads, express checkouts included. See Shopify Conversions API.
• Hand evidence to Google. On the Organization plan, the fraud refund report exports bot-flagged Google Ads clicks in the format Google's Click Quality form asks for. You attach it; Google decides.

What the Gateway does

From Meta's developer documentation: the Gateway is a self-serve option in Events Manager. You provision a server instance in your own cloud environment, using templates Meta provides, and point a subdomain at it. The Meta Pixel then sends browser events both to Meta and to the Gateway, and the Gateway forwards them to the Conversions API. Meta uses an event ID to deduplicate the two copies.

• A request to your own domain. The pixel call goes to a subdomain of your site, which helps where blockers act on Meta's own domains.
• A server to server copy. The event also reaches Meta from your server, so a closed tab does not lose it.
• No custom build. Meta describes it as cutting integration time from weeks to hours.

What it costs to run

Meta does not charge for the Gateway software. You pay your cloud provider for the resources it runs on, and you own its uptime and updates. A server that is down is a tracking gap you find out about later. Budget for someone to watch it, not only for the first setup.

What it leaves to you

• Consent. The Gateway forwards what the pixel sends. Whether a visitor agreed is a decision your banner and your setup have to carry through. Check that a declined visitor's events are not sent.
• Who the events came from. A forwarded event from a bot looks like any other. Hashing and matching make a bot event tidier, not truer, and Meta then learns from it.
• The sale after the form. A booked call or won deal happens in your CRM. A pixel gateway sees your website.
• Other platforms. It is a Meta product. Google Ads, TikTok and LinkedIn each need their own route.
• Deduplication drift. A theme update or a new app can change event IDs and double count. Watch the deduplication view in Events Manager after any change.

How to check your Gateway

1. Open Test Events in Events Manager and place a real test order or lead.
2. Look at the source. Each event should show as received from both the browser and the server.
3. Check deduplication. One order should be one counted purchase, not two.
4. Test a declined visitor. Decline your consent banner and confirm nothing identifiable is sent.
5. Test after every deploy. The things that break it are boring: a changed event ID, an updated theme, a new app.

What goes around the Gateway

The Gateway can stay as the Meta delivery layer. What belongs around it is a check on what goes in and the sales that come after. DataCops does that without a container to run: one script and one DNS record on your own domain, a bot verdict on every visit with a Real people only switch per ad platform, the sale from your CRM or Shopify sent back to Meta, Google Ads, TikTok and LinkedIn, and a log of every send. Where you do not want to run a server at all, it can replace the Gateway for the same Meta job. See the Meta Conversions API page and how the tools compare.

Deliver reliably, then decide what deserves to be delivered.

FAQ

Can I warm up a new campaign with my existing customers?

Yes, with DataCops Ads Warmup. Upload a CSV of customers (only email is required, up to 20,000 rows), see a 0 to 10 match score for each person, and send them to Meta, Google Ads and TikTok, dated when you send. Google Ads credits only people who clicked a Google ad.

What is the Facebook Conversions API Gateway?

A self-serve option in Meta Events Manager. You provision a server in your own cloud account and point a subdomain at it. The pixel sends events to Meta and to your Gateway, which forwards them server to server, deduplicated by event ID.

Does the Gateway filter bots?

Not as described in Meta's documentation. It forwards events. Whether a visitor was a real person is not part of its job.

Does the Gateway handle consent?

It forwards what the pixel sends, so consent has to be handled by your banner and your setup. Test that a declined visitor's events are not sent.

Does the Gateway send CRM sales to Meta?

No. It forwards pixel events from your website. Sales that close in a CRM need a separate route.

Can DataCops replace the Gateway?

For the Meta delivery job, yes, without running a server: one script and one DNS record. It also sends to Google Ads, TikTok and LinkedIn. If you need the Gateway's specific cloud deployment, keep it.

Sources

• Meta for Developers: Conversions API
• Meta for Developers: handling duplicate pixel and Conversions API events
• Meta for Developers: Conversions API Gateway