Meta Conversions API for Video Sales Funnels
Send server-side conversion events from AtomicPlayer to Meta, with the play_id, revenue amount and video variant attached. Meta Ads can then optimise for actual purchases, not clicks, because it receives conversion data directly from the server.
What Is the Meta Conversions API?
The Meta Conversions API, also called Meta CAPI or the Facebook Conversions API, lets conversion data reach Meta directly from a server rather than only from the browser. AtomicPlayer uses it for server-side tracking: it sends conversion events to the Meta Conversions API with the play_id, revenue amount and video variant attached, so Meta Ads can optimise for actual purchases instead of clicks.
What Does the Meta Conversions API Integration Do?
Optimize on real revenue
Each event sent to Meta includes the revenue amount, so Meta Ads receives purchase value, not only a click.
Server-side from your checkout
AtomicPlayer attributes revenue natively to Stripe, Hotmart, Kiwify, Shopify and PayPal, then forwards purchases to Meta.
Ad and second that converted
Pair Meta’s ad attribution with AtomicPlayer’s second-by-second retention to see which creative and which second sold.
Break down by variant
Every event carries the video variant, so A/B winners on the sales video show up in Meta optimizations.
AI on Meta cohorts
Atomicat flags shifts such as a drop in a Meta Ads cohort across sources and regions.
Multi-platform ready
Send the same attributed conversions to Meta, Google Ads Enhanced Conversions and TikTok Ads.
Which Funnels Need Server-Side Tracking for Meta Ads?
Facebook video ads to a VSL
Cold traffic watches the sales video, sees a time-triggered CTA and buys — Meta gets the purchase, not just the click.
Infoproduct funnels
Checkouts on Hotmart, Kiwify, Eduzz or Monetizze, attributed natively then forwarded to Meta.
Stripe, Shopify and PayPal
Base Facebook ads conversion tracking on paid orders rather than thank-you page pixels alone.
Scaling spend
Move budget based on attributed revenue by traffic source, not on view counts.
How Does the Meta Conversions API Work With AtomicPlayer?
Five steps
1) Start free and host your sales video. 2) Connect your checkout. 3) Connect Meta Ads from ads and attribution integrations. 4) Let AtomicPlayer send server-side events on attributed sales. 5) Compare Meta’s reported results with AtomicPlayer’s multi-touch attribution and optimise.
Meta Conversions API questions, answered.
CAPI is short for the Meta Conversions API, also known as the Facebook Conversions API.
It lets conversion data reach Meta directly from a server rather than only from the browser.
The Meta Pixel, formerly the Facebook Pixel, is Meta’s browser-based tracking code on your web pages.
The Conversions API sends the same kinds of events from your server, which improves reliability when browsers block cookies or scripts.
A viewer watches your AtomicPlayer video and buys through your checkout.
AtomicPlayer attributes the sale to that play, then sends a server-side purchase event to the Meta Conversions API with the play_id, revenue amount and video variant.
Each server-side event includes the play_id, the revenue amount and the video variant.
Developers can extend payloads via the API when needed.
The Conversions API Gateway is Meta’s own tool for sending events server-side.
AtomicPlayer already sends attributed purchase events to Meta, so you do not need a separate gateway for video-attributed sales.
AtomicPlayer attributes revenue natively to Stripe, Hotmart, Kiwify, Shopify and PayPal through first-party integrations, plus Eduzz and Monetizze, then forwards attributed purchases to Meta.
Yes.
AtomicPlayer also sends server-side conversions to Google Ads Enhanced Conversions and feeds play-level conversions into TikTok Ads optimization.
Meta applies the attribution setting of your ad set.
AtomicPlayer’s own reports offer multi-touch attribution with ROAS and revenue per play alongside Meta’s view.
Event match quality is Meta’s score, shown in Events Manager, for how well the events you send can be matched to people in Meta’s systems.
Richer server-side events generally improve that score.
A ThruPlay is Meta’s count of video ad plays that reach at least 15 seconds or the end of the video, whichever comes first.
It measures ad video consumption, not AtomicPlayer sales-page retention.
Revenue attribution is included on Pro at $79 a month, which starts with a 14-day trial, and on Scale.
Start free to host and embed, then upgrade to connect Meta Ads.
Give Meta the Sales Your Video Actually Made
Start free, host your sales video and embed it in 30 seconds. Upgrade to Pro when you are ready to attribute revenue and send Meta CAPI events. Selling on Hotmart? See the Hotmart integration page.