Conversions API: What It Is and Why DTC Brands Need It

Home / Glossary / Conversions API

The Conversions API is a way to send customer events from your website's server straight to Meta. It works alongside the Meta pixel, which tracks events in the visitor's browser. Because browsers, ad blockers and privacy settings can stop the pixel from firing, the conversions api acts as a second, more reliable line of tracking.

For ecommerce brands, this matters because Meta's delivery system learns from purchase data. The more accurately purchases are reported, the better Meta can find similar buyers. TikTok and Google have their own server-side tools that work on the same principle.

What is the Conversions API?

The Conversions API, often called CAPI, is Meta's server-side tracking tool. It sends events such as purchases and add to carts directly from your store's server to Meta, instead of relying only on the browser pixel. That fills gaps caused by ad blockers and browser privacy limits, giving Meta better data to optimise your campaigns.

Conversions API (CAPI): The Conversions API is Meta's server-side tracking tool that sends website events like purchases directly from your server to Meta for attribution and optimisation.

How the Conversions API works

When a customer views a product, adds to cart or buys, your store sends that event to Meta from the server, along with hashed customer details such as email and phone number. Meta matches those details to user accounts to attribute the event. Because the pixel often sends the same event from the browser, each event carries an event ID so Meta can remove duplicates.

On Shopify, the simplest route is connecting the Facebook and Instagram sales channel with maximum data sharing, which turns on server-side events. Other platforms use partner integrations or a custom setup.

Worked example (illustrative numbers): a store records 1,000 orders in a week but the pixel reports only 820, so Meta sees 82% of purchases. After setting up CAPI with deduplication, Meta reports 950, or 95%. The campaigns have not changed, but Meta now learns from 130 more purchases each week.

What good tracking depends on

There is no perfect match between store orders and Meta-reported purchases, because attribution windows and cross-device behaviour always create gaps. The goal is to send as many accurate events as possible, deduplicated, with strong customer information. Meta's Events Manager shows an Event Match Quality score out of 10 for each event, which is a useful guide. Quality depends on:

Customer parameters sent: email, phone, name, location and external ID all improve matching.
Deduplication: browser and server events need matching event IDs.
Event timing: events should be sent close to when they happen.
Coverage: key events such as view content, add to cart, initiate checkout and purchase should all be sent.
Consent handling: tracking must respect the privacy rules in each market you sell to.

How to improve Conversions API data

Start by checking Events Manager for each core event. Look for warnings about duplicate events, missing parameters or low match quality. If purchase match quality is low, send more customer information where you have consent, especially email and phone at checkout.

Compare Meta-reported purchases with store orders each week. A large, sudden gap usually means something broke, such as a theme change, a new checkout app or an expired integration. Test the full purchase flow after any store update. Make sure purchase value and currency are passed correctly, because value-based optimisation and ROAS reporting depend on them. Tracking and CAPI are the first job in our Foundation phase, during the first 14 days of every engagement.

Common Conversions API mistakes

Sending server and browser events without matching event IDs, which double counts purchases.
Passing too few customer details, leaving match quality low.
Installing several apps that all send purchase events.
Sending purchase values without currency or with tax and shipping handled inconsistently.
Assuming setup is permanent and never checking it after store changes.

Related terms

The Conversions API feeds Meta's attribution, so it interacts closely with attribution windows. Automated campaigns such as Advantage+ rely heavily on clean purchase signals. Blended ROAS gives you a store-level view that does not depend on tracking at all, which makes it a useful cross-check. Our Facebook ads for Shopify guide covers the setup steps.

A simple monthly health check keeps tracking honest. Pull store orders and Meta-reported purchases for the same dates, note the ratio, and log Event Match Quality for the purchase event. If either number drops noticeably from one month to the next, investigate before changing campaigns. Many performance problems that look like creative or audience issues turn out to be tracking breaks after a theme or app update.

Proof from real accounts

Days 1-14 Tracking and CAPI setup: Part of the Foundation phase in every engagement
$50M+ Meta ad spend managed: Across our client accounts
2.82x ROAS at high spend: $374,103 revenue on $132,832 spend in 16 days (see the proof)

Frequently asked questions

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

Yes. Meta recommends using both together. The pixel captures browser events and some details the server may not have, while the Conversions API fills gaps when the browser blocks tracking. With deduplication through matching event IDs, Meta combines the two into one more complete record of what customers did on your site.

How do I set up the Conversions API on Shopify?

The usual route is through the Facebook and Instagram sales channel app. Connect your Meta business account, pixel and catalogue, then choose the maximum data sharing setting, which enables server-side events. Afterwards, check Events Manager to confirm purchases arrive from both browser and server and are being deduplicated correctly.

What is Event Match Quality?

Event Match Quality is a score from 0 to 10 in Meta Events Manager that shows how well the customer information you send can be matched to Meta accounts. Higher scores mean more events are attributed correctly. You raise it by sending more customer parameters, such as email, phone and location, where you have the right consent.

Will the Conversions API make my ROAS look better?

It often increases reported purchases because Meta sees conversions it was missing before. That makes reported ROAS more accurate rather than artificially better. The bigger benefit is optimisation: with more purchase data, Meta finds buyers more efficiently, which can improve real results. Always cross-check with store revenue and blended ROAS.

Is the Conversions API only for Meta?

The name usually refers to Meta, but other platforms offer similar server-side tracking. TikTok has its Events API and Google offers enhanced conversions and server-side tagging. They work on the same idea: sending conversion data from your server with hashed customer details. Most DTC brands running several platforms should set up each one.

Not sure your tracking is telling the truth?

A Brand Growth Audit includes a review of your pixel, Conversions API and event setup so Meta optimises on accurate purchase data. Book a Brand Growth Audit.