The Meta Conversions API (often called CAPI) sends conversion events from your server to Meta, instead of relying only on the browser. It helps fill gaps left by browser privacy settings and blocked pixels, and it improves how well your ads can find and measure customers.

The problem it solves

Browser-based tracking can be blocked or limited by privacy settings, ad blockers, cookie rules and app-level restrictions. When the pixel misses a conversion, Meta cannot learn from it or report it. That makes campaigns look worse than they are and starves the algorithm of signal.

How CAPI works

Instead of depending on the visitor’s browser, your website, booking system or CRM sends the event directly to Meta from your server, along with details such as the event type and customer information that has been handled according to privacy requirements. Meta matches it to the ad interaction.

Key takeaways

  • CAPI sends events server to server, not just from the browser.
  • It works alongside the pixel, with duplicates removed.
  • Better data improves optimization and measurement.
  • Setup ranges from built-in integrations to custom builds.

Pixel plus CAPI is best

Meta recommends using both. The pixel captures what happens in the browser; CAPI captures what happens on your side. Events are tagged so Meta can deduplicate, counting one conversion once even if both report it.

How owners usually set it up

Many platforms offer direct integrations, including Shopify, WooCommerce, WordPress plugins, tag managers and CRMs. A custom setup may be needed for booking tools or offline sales. Whichever route, test in Events Manager and review the event match quality score.

Offline and phone conversions

CAPI can also send events from outside the website, such as a booked appointment, a closed deal or an in-store purchase. This lets Meta optimize for real revenue rather than form fills, which is powerful for service businesses.

What to ask your agency

Is CAPI installed? How is deduplication handled? What is our event match quality? Which events are sent? Can offline sales be uploaded? These questions separate teams that manage tracking carefully from those that only set up ads.

A practical setup path for small businesses

  • Start with the integration your platform offers (Shopify, WordPress plugins or a tag manager).
  • Check that the same event is sent from both browser and server with a shared event ID.
  • Review match quality and fix missing customer details where permitted.
  • Add offline events, such as closed deals, once the basics work.
  • Document the setup so it survives site changes.

Example: a service business with phone sales

A home-services company gets leads online but closes sales by phone. By sending a ‘Purchase’ or ‘Closed Job’ event to Meta through the Conversions API after each sale, the company teaches Meta which leads become customers. Over time the system finds more people like those buyers instead of more form fillers.

Questions owners ask

Does it slow my site? No, server events run on the back end. Does it replace consent rules? No, you must still follow privacy laws and your own policies. How do I know it works? Events Manager shows server and browser events, deduplication and match quality for each event.

Frequently asked questions

Is CAPI required?

Not strictly, but running without it often means weaker data and results.

Is it complicated?

Integrations make it simple for many setups; custom needs take more work.

Does CAPI replace the pixel?

No. They are designed to work together.

Is customer data safe?

Data is sent according to Meta’s requirements and your privacy policy; always follow applicable laws.

Related reading

Want tracking you can trust? We’ll set it up ⟶

Work with Sitting Pretty Creative

Want this done for you?

We are a growth marketing and AI agency in New York City and San Diego. Tell us where your business is today and we will come back with a plan and a budget that makes sense.

Let’s make something happen ⟶Explore Paid Social Advertising ⟶