How ClickFortify handles the Conversions API
CAPI proxy (when enabled)
ClickFortify checks conversions sent through it against the visitor’s fraud score and drops or tags flagged events before Meta receives them.
Suspicious conversions flagged
On Meta, a conversion within 2 seconds of the click, a bot that converted and devices with 3 or more conversions are flagged.
Meta clicks tracked via fbclid
ClickFortify tracks every Meta click through fbclid and scores it on device, network and behavior signals.
Audience Network controls (opt-in)
Use a publisher block list or switch Audience Network off per ad set. Block lists need a Meta Business Manager.
The Meta Conversions API (CAPI) is a server-side interface that lets advertisers send conversion events (purchases, leads, signups, add-to-carts) from their own server directly to Meta. It was built to complement (and increasingly replace) the browser-based Meta Pixel, which loses data to ad blockers, browser privacy features, and connection drops. Because CAPI events originate from your infrastructure rather than the visitor’s browser, you decide exactly which events Meta receives.
That last property is what makes CAPI matter for fraud protection. The Pixel fires for every visitor: humans, bots, and click fraud traffic alike. CAPI gives advertisers a checkpoint where conversion events can be validated before Meta ever sees them.
For setup and how fraud filtering changes what Meta optimizes toward, compare Meta Pixel vs CAPI for fraud-filtered conversions.
How the Conversions API works
When a visitor completes a conversion action on your site, your server (or a connector acting on its behalf) constructs an event (containing the event name, timestamp, and matching parameters like hashed email or click ID) and posts it to Meta’s endpoint. Meta deduplicates it against any matching Pixel event, attributes it to the ad interaction that drove it, and feeds it into delivery optimization and reporting.
The practical differences from the Pixel:
- Reliability: server events are not affected by ad blockers, ITP, or users bouncing before scripts load.
- Data quality: you can enrich events with information the browser never had, like CRM lead status or validated order value.
- Control: events can be inspected, corrected, delayed, or dropped before they reach Meta.
Pixel vs. Conversions API
The Pixel is declared by the browser: whatever loads the page can fire it, which is precisely why bots inflate Pixel-based conversion counts. CAPI is asserted by your server: nothing reaches Meta unless your systems decide it should. Most advertisers run both in parallel with event deduplication: the Pixel for coverage and match quality, CAPI for reliability and control. But only the CAPI path can act as a fraud filter, because only there does an event pass through logic you own.
Why conversion signal quality decides Meta Ads performance
Meta’s delivery system (including Advantage+) works by finding more users who resemble the people who already converted. That makes the conversion signal the steering wheel of the entire account. When invalid traffic and fake leads register as conversions:
- Reported ROAS and cost-per-lead look better than reality, hiding the damage.
- Delivery optimization actively seeks out more users who look like the bots and click farms that “converted.”
- Lookalike and retargeting audiences get seeded with fraudulent profiles, so the pollution compounds across campaigns.
Unlike Google Ads, Meta offers no IP exclusion lists, so you cannot simply block the offending sources at the platform level. Protecting the signal is the lever that actually works on Meta.
Fraud-filtered CAPI: the ClickFortify approach
ClickFortify uses the Conversions API as a fraud checkpoint and scores every click and session against 100+ device, network and behavior data points, including device fingerprinting and behavioral analysis. When the CAPI proxy is enabled, conversion events are checked server-side against the visitor’s fraud score: events from flagged visitors, such as bots that converted, are dropped or tagged before Meta receives them. ClickFortify also flags suspicious conversions, such as a conversion within 2 seconds of the click or a device with 3 or more conversions.
Your Pixel keeps running as normal; nothing about your tracking setup has to be rebuilt. You can see how it fits into the full protection stack on our Meta Ads click fraud protection page.
Key takeaways
- The Meta Conversions API sends conversion events server-to-server, making tracking more reliable and fully controllable.
- The Pixel fires for every visitor, fraud included; CAPI is the only path where events can be validated first.
- On Meta, polluted conversion signals retrain delivery toward junk traffic, so fraud compounds instead of just wasting clicks.
- When the CAPI proxy is enabled, ClickFortify checks the conversions sent through it against the visitor’s fraud score and drops or tags flagged events before Meta receives them.