Meta Conversions API and server-side tracking, explained

Your browser pixel misses conversions every day. Here is how the Conversions API fills the gap, how deduplication works, and what to send.

Rows of server racks in the Indian Railways 139 helpline server room
Photo: Indrajit Das, CC BY-SA 3.0, via Wikimedia Commons

Meta's Conversions API (CAPI) sends conversion events from your server or CRM straight to Meta, instead of relying only on the Meta Pixel running in a shopper's browser. You run both, give each event the same event_id and event_name so Meta keeps one copy, and attach hashed customer details (email, phone) plus the fbp and fbc cookie values so Meta can match the event to a person. Done right, it recovers conversions the browser loses and gives Meta's delivery models the signal they optimise on.

Key takeaways
  • Pixel + CAPI, not one or the other: Meta's own guidance is a redundant setup.
  • event_id + event_name within 48 hours is how Meta keeps one copy of a conversion.
  • 31%: how much the median cost per incremental customer rose without offsite data, in a 70,000-advertiser Meta experiment.
  • SHA-256: email, phone and name must be normalised and hashed; fbp, fbc, IP and user agent are never hashed.
  • Send the event that matches money: delivered COD orders and CRM enrolments, not just form fills.
  • DPDP Rules (notified 14 Nov 2025): hashing does not make data consent-free.

This matters more each year because Meta's ad system has moved its intelligence into automated delivery. As I explain in how Meta Andromeda and Advantage+ pick ads, retrieval and ranking now decide who sees an ad, and they learn from the conversions you report.

Under-reporting doesn't just make your dashboard look bad. It teaches the system the wrong lesson about which people convert.

Why does the Meta Pixel miss conversions?

The Meta Pixel misses conversions because it is JavaScript running in the visitor's browser, so anything that stops the script or its cookies stops the event.

The story

On 16 December 2020, Facebook bought full-page ads in The New York Times, The Wall Street Journal and The Washington Post with one headline: it was standing up to Apple for small businesses everywhere. Apple was about to make every iPhone app ask users before tracking them across other companies' apps and sites.

Facebook claimed that ads without personalised targeting produced 60% fewer sales, though it did not show the data behind the figure. Apple replied that Facebook wanted to collect as much data as possible. Apple went ahead in 2021, and later research measured what followed: a 37% drop in click-through rate for conversion-optimised Meta ads. Server-side tracking through the Conversions API became the industry's main answer to that change.

MacRumors: Facebook takes out full-page newspaper ads to attack Apple's iOS privacy changes (16 Dec 2020)

Three forces do most of the damage:

  • App Tracking Transparency (ATT). Since Apple's 2021 rollout, apps must ask permission before tracking users across other companies' apps and sites. Many users decline, which blocks the device advertising ID and cuts the signal Meta gets from iPhone users who click an ad inside Facebook or Instagram.
  • Browser cookie limits. Safari, Firefox and Brave block third-party cookies by default. Chrome reversed its plan to drop them: on 22 April 2025 Google said cookies would stay available by default, and on 17 October 2025 it retired most Privacy Sandbox APIs. The cookie situation depends on which browser your customer uses, and many Indian iPhone buyers sit in the most restricted group.
  • Blockers and broken pages. Ad blockers, privacy extensions, slow-loading thank-you pages, and payment gateways that redirect without returning to your site all stop the pixel from firing.
Bundle of network cables plugged into a network switch
Server-side tracking moves the conversion event from the shopper's browser to a machine you control.Photo: ProjectManhattan, CC BY-SA 3.0, via Wikimedia Commons

What the lost data costs

The cost of losing that data is measurable. Two large studies put numbers on it, one using Meta's own experiment infrastructure and one using e-commerce firms' revenue.

StudyHeadline numberWho lost most
Wernerfelt et al., 70,000+ advertisersCost per incremental customer up 31% without offsite dataSmall advertisers
Aridor et al., ATT and e-commerce37% lower click-through on conversion-optimised Meta adsSmaller firms
Estimating the Value of Offsite Tracking Data to Advertisers: Evidence from MetaNils Wernerfelt, Anna Tuchman, Bradley Shapiro, Robert Moakler · Marketing Science 44(2), 2025 (NBER WP 32765)

The authors ran a randomised experiment with more than 70,000 advertisers on Facebook and Instagram, comparing normal delivery with delivery that could not use offsite data (pixel and similar signals from advertisers' own sites). The median cost per incremental customer was $38.16 with offsite data and would rise to $49.93 without it, a 31% increase. Offsite data also produced more long-term customers per dollar, and losing it hurt small advertisers the most. Limit: the setting is Meta's own platform, so results are specific to Meta's systems as they were at the time of the experiment.

Read the paper (free)
Evaluating the Impact of Privacy Regulation on E-Commerce Firms: Evidence from Apple's App Tracking TransparencyGuy Aridor, Yeon-Koo Che, Brett Hollenbeck, Maximilian Kaiser, Daniel McCarthy · CESifo Working Paper 10928, 2025

Using new datasets on advertiser spending, ad performance and firm revenue, the authors measured what ATT did to e-commerce businesses. Conversion-optimised Meta ads, the kind most affected by ATT, saw a 37% drop in click-through rate after ATT. Firms moved spend toward Google, but those that depended more on Meta still lost revenue relative to less exposed firms, with estimates between 8% and 40% depending on method. Smaller firms bore most of the loss. Limit: the sample is mostly US e-commerce, and revenue effects vary widely across methods.

Read the paper (free)
Median cost per incremental customer on Meta, with and without offsite data
See the data as a table
Median cost per incremental customer ($)
With offsite data (baseline)38.16
Without offsite data49.93

Source: Wernerfelt et al., Marketing Science 2025 (NBER WP 32765), experiment with 70,000+ advertisers · A 31% increase at the median. An earlier working-paper version reported $43.88 rising to $60.19.

How does the Conversions API work?

The Conversions API is an HTTPS endpoint: your server posts a JSON payload for each event (name, time, value, currency, and customer details) to Meta's Graph API, and Meta matches it to a user and feeds it to measurement and delivery.

Meta describes it as a way to connect data from your server, website platform, app or CRM to optimise targeting, lower cost per result and measure outcomes.

BrowserMeta Pixel firesYour serverorder, CRM, paymentsame event_idblocked by ATT, blockers, cookiesConversions API (HTTPS)Meta1. dedupe: event_id + name, 48 h2. match: hashed email, phone,fbp, fbc, IP, user agent3. report and optimise
A redundant setup: the pixel and the server send the same event with the same ID, and Meta keeps one. If the browser path fails, the server path still arrives.

Meta's own guidance is to run CAPI alongside the pixel, not instead of it. Your setup options:

  • Existing pixel: Events Manager offers a one-click CAPI setup for website events.
  • Shopify and large e-commerce platforms: native integrations.
  • Custom stacks: call the endpoint directly or use a server-side tag manager.
QuestionMeta Pixel (browser)Conversions API (server)
Where it runsVisitor's browser, JavaScriptYour server, platform or CRM
Blocked by ad blockers and ATTOftenNo, but matching gets harder without identifiers
Sees post-purchase events (delivery, refund, qualified lead)NoYes, if your systems send them
Collects IP and user agentAutomaticallyYou must pass them
Reads fbp and fbc cookiesAutomaticallyYou must read and forward them
Setup effortLowLow on Shopify; medium to high on custom stacks

How does deduplication between Pixel and CAPI work?

Meta deduplicates when the pixel's eventID matches the server's event_id and the event names match, for events reaching the same pixel within 48 hours. When both copies are similar, Meta generally keeps the one that arrived first and discards the later one.

There is a fallback that uses event_name plus fbp or external_id, but it is weaker: it generally works only when the browser event arrives first and the server event follows within 48 hours, and it never removes duplicates between two browser events or two server events.

The practical rule

  1. One ID per conversion. The order ID works well.
  2. Same ID in both calls. Put it in the pixel call and the server call.
  3. Same event name, same case. "Purchase" everywhere.
  4. Retries keep the ID. Never let a retry create a new one.

What customer data should you send, and how?

Send as many valid match keys as you lawfully hold: hashed email and phone at minimum, plus the fbp and fbc cookie values, the client IP address and user agent, and an external_id. Meta requires contact fields to be normalised and SHA-256 hashed before sending.

Preparing a match key 1. Raw from your form " Name@Example.COM " 2. Normalise: trim, lowercase "name@example.com" 3. SHA-256 hash, send as "em" 64 hex characters, same every time Never hash: fbp, fbc, IP, user agent pass them exactly as read from the request
Normalisation comes before hashing: "Name@Example.COM" and "name@example.com" give different hashes, and only one of them will match. Rules from Meta's customer information parameters page.
ParameterWhat it isHash?Format rule
emEmailSHA-256Trim spaces, lowercase
phPhoneSHA-256Digits only with country code, no leading zeros (an Indian mobile becomes 91 followed by 10 digits)
fn, lnFirst and last nameSHA-256Lowercase letters, no punctuation
ct, st, zp, countryCity, state, postcode, countrySHA-256Lowercase, no spaces; country as two-letter ISO code (in)
external_idYour customer IDRecommendedSame format everywhere you send it
fbp, fbcMeta browser ID and click ID cookiesNeverPass exactly as read from _fbp and _fbc
client_ip_address, client_user_agentVisitor IP and browser stringNeverReal values from the request; user agent is required for website events

Event Match Quality

Meta scores how well your events match with Event Match Quality, a 0 to 10 score per event in Events Manager. It is currently available only for web events, and Meta notes that only matched events can be used for attribution and delivery optimisation.

An ornate antique cash register on a counter in a café in Darjeeling
The till always knew the true sale. Server-side tracking is the digital version of trusting the till over the doorway counter.Photo: Subhrajyoti07, CC BY-SA 4.0, via Wikimedia Commons

How do you check whether your pixel is under-counting?

Compare the conversions Meta reports (all attribution windows, all campaigns) with the orders or leads in your own backend for the same period and the same traffic source.

The gap is not all lost tracking, because some orders come from other channels, but a trend in the gap after a fix tells you whether the fix worked. Use this to check what you just read.

How much is your browser pixel capturing?

What should Indian D2C and edtech teams send through CAPI?

Send the event that matches real money, not the one that is easiest to fire. For many Indian businesses that is not the default browser Purchase or Lead event.

  • Cash-on-delivery D2C. A COD order created is not revenue until it is delivered. Send Purchase at order creation for speed, and send a custom delivered or RTO event from your logistics system so you can build reporting and audiences on real sales. The COD and RTO guide covers the operations side.
  • Edtech and B2B lead generation. A form fill is a weak signal. Send CRM stages (contacted, qualified, application, enrolment) back through CAPI with the lead's hashed email and phone, so optimisation moves toward people who enrol. This is the idea behind measuring cost per enrolment, not cost per lead.
  • Payment gateway redirects. UPI and card flows that leave your domain often break the thank-you page pixel. Fire the server event from the payment webhook instead.

Does CAPI fix attribution?

No. CAPI improves the data Meta receives, which improves delivery and reduces under-reporting, but Meta still attributes conversions using its own windows and models, and it will still claim some sales that would have happened anyway.

Server-side tracking is an input, not a measurement strategy.

The r/analytics thread on multi-touch attribution reached a similar place. One practitioner said their team stopped hunting for a single correct attribution number; another pointed out that on iOS the top of the journey is invisible, so path-based models rebuild journeys from the cheap, visible end.

The fix is a stack: platform data for daily optimisation, controlled lift or geo tests for causal checks, and marketing mix modelling for budget splits. Meta's open-source Robyn MMM, for example, uses aggregated spend and outcome data with no personal data or pixel signals, and can be calibrated against lift tests.

I cover the full stack in the attribution measurement stack after cookies and compare Meridian and Robyn separately.

LayerCapturesMisses
Pixel onlyOn-site events in browsers that allow itBlocked browsers, broken redirects, offline and CRM outcomes
Pixel + CAPIMost web events, plus CRM and offline events you sendCausality: whether the ad caused the sale
Lift or geo testsIncremental effect of a campaign over a holdoutAlways-on coverage; tests are periodic
MMM (Robyn, Meridian)Channel contribution from aggregate data, no user trackingAd-level and creative-level detail

Fixing the server signal is often the cheapest performance gain available, because it improves both what Meta optimises toward and what you can trust in reporting. The Wernerfelt experiment above is the evidence: losing offsite data raised the cost of an incremental customer by 31%. If you want to see how I approach marketing for growth teams, the work page has examples.

Questions people ask

Do I still need the Meta Pixel if I use the Conversions API?

Yes, for websites. Meta recommends a redundant setup. The pixel automatically collects IP, user agent and the fbp and fbc cookies that help matching, and it captures browsing events your server never sees. CAPI covers the events the browser loses.

Why did my reported conversions double after setting up CAPI?

Almost always broken deduplication. Check that the browser eventID and the server event_id are identical for the same conversion, that event names match exactly including case, and that both reach the same pixel within 48 hours.

Is server-side tracking legal in India?

Server-side sending is a transport method; the legal question is whether you have a lawful basis and consent to share the personal data. The DPDP Act 2023 and the Rules notified in November 2025 apply whether data goes via browser or server. Hash contact fields as Meta requires and follow your counsel's consent design.

What is a good Event Match Quality score?

Meta does not publish a target. Treat the score as a diagnostic: if it is low, add the missing keys (hashed email and phone, external_id, fbp, fbc, IP, user agent) and check normalisation, such as phone numbers with the 91 country code.

Sources

  1. Meta for Developers: Conversions API (2026)
  2. Meta for Developers: Deduplicate Pixel and server events (2026)
  3. Meta for Developers: Customer information parameters (2026)
  4. Meta for Developers: Conversions API best practices (2026)
  5. Wernerfelt, Tuchman, Shapiro, Moakler: Estimating the Value of Offsite Tracking Data to Advertisers, NBER WP 32765 / Marketing Science (2025)
  6. Aridor, Che, Hollenbeck, Kaiser, McCarthy: Evaluating the Impact of Privacy Regulation on E-Commerce Firms, CESifo WP 10928 (2025)
  7. Kollnig et al.: Goodbye Tracking? Impact of iOS App Tracking Transparency and Privacy Labels, FAccT (2022)
  8. Stape: Google Chrome cookie deprecation explained (2025)
  9. Press Information Bureau: DPDP Rules, 2025 notified (2025)
  10. Haus: Meta announces new health and wellness conversion restrictions (2024)
  11. Meta Marketing Science: Robyn open-source MMM (2026)
  12. MacRumors: Facebook takes out full-page newspaper ads to attack Apple's iOS privacy changes (Dec 2020)
conversions apiserver-side trackingmeta pixelevent match qualitydeduplicationattribution
Sapta

Sapta (Saptarshi Sarkar) is a mechanical engineer turned marketer in Bengaluru and a solo touring rider. He writes the seven Saptaverse blogs. Work with him or read more of Marketblog.

Keep reading in Marketblog

From the other blogs