What CAPI does differently
The Conversions API sends each conversion event directly from your server to Meta. It bypasses the browser, so there is no tracker to block or data lost to browser blocking.
Meta trains its targeting algorithm on conversion data. A more complete signal improves targeting over time, as well as reporting in Events Manager.
Most CAPI implementations overlook how better data changes targeting over the following weeks, as the algorithm relearns the audience that buys.
Run the pixel and CAPI together
The common mistake is replacing the browser pixel with CAPI. The correct architecture is running both simultaneously.
The pixel fires immediately on page events, captures first-party cookies and sends click IDs. CAPI sends every conversion from the server regardless of browser state. Meta uses event_id to deduplicate them, preventing double-counting.
When both fire, Meta records the event once with the best available data. If the pixel is blocked, CAPI still captures the conversion.
// Server-side CAPI event (Node.js)
const { Facebook } = require('facebook-nodejs-business-sdk');
async function sendConversionEvent(req, purchase) {
const userData = new Facebook.UserData()
.setEmail(hash(purchase.email))
.setPhone(hash(purchase.phone))
.setClientIpAddress(req.ip)
.setClientUserAgent(req.headers['user-agent'])
.setFbc(req.cookies._fbc)
.setFbp(req.cookies._fbp);
const customData = new Facebook.CustomData()
.setValue(purchase.total)
.setCurrency('EUR')
.setOrderId(purchase.id);
const event = new Facebook.ServerEvent()
.setEventName('Purchase')
.setEventTime(Math.floor(Date.now() / 1000))
.setEventId(`purchase_${purchase.id}`) // for deduplication
.setUserData(userData)
.setCustomData(customData)
.setActionSource('website');
const eventsData = [event];
const eventRequest = new Facebook.EventRequest(PIXEL_ID, eventsData);
await eventRequest.execute();
}Fields that improve match quality
Not all CAPI fields have equal impact on match quality. In order of importance:
Hashed email is consistently the strongest identifier. Send it when available at conversion time, as it is for any logged-in purchase.
fbc and fbp cookies (Meta's click ID and browser ID cookies) are critical for connecting CAPI events back to ad clicks. They need to be read server-side before the event fires, which means your server needs access to the first-party cookies set by the pixel.
IP address and user agent are weaker individually but meaningful in aggregate, especially for matching anonymous browsing sessions.
Phone number matters if your acquisition channel is phone-based. For most web purchases, email dominates.
The Event Match Quality score in Meta's Events Manager (0-10) reflects how much of this data you're including and how cleanly it's formatted. Scores above 7 typically indicate a solid implementation. Below 5 suggests missing fields.
The timeline for results
CAPI doesn't improve results on day one. The Meta algorithm needs time to relearn the conversion audience with the corrected, more complete data signal.
Meaningful targeting improvements typically appear in 3-4 weeks as the model updates its audience profile. Campaign conversion rates improve gradually as ads reach people who better match the corrected purchase data.
The way to measure it: compare the conversion audience (from CAPI) to the audience your campaigns were targeting before implementation. If they're different, the algorithm was working from bad data.
Businesses running Meta ads at meaningful scale need CAPI. The pixel alone supplies incomplete data for targeting; CAPI provides a straightforward fix.