What Is Meta CAPI (Conversions API)?

What is Meta CAPI? CAPI is short for Meta’s Conversions API (formerly the Facebook Conversions API): a way to send conversion events to Meta Ads directly from a server, without depending on a script (the Pixel) running in the browser of the person who converted. Other ad platforms have the same concept under other names, but “CAPI” specifically refers to Meta’s API.

Why it exists

The Meta Pixel is JavaScript that runs on a web page. It works well wherever there’s a browser and a page, but it loses signal to ad blockers, privacy restrictions, or simply because the event happens outside any browser. CAPI solves this by letting the backend of an app, bot or tool confirm the event itself, in a way that’s much more resistant to that kind of signal loss.

Meta CAPI and Telegram

On Telegram, the difference is more radical: the channel join happens inside the app, with no browser or page running. So CAPI stops being a complement to the Pixel and becomes the only possible path for that event to reach Meta. It’s through CAPI that Track4you sends channel entries (enter_channel) and exits (left_channel) to your pixel — and, through its Integrations (Pro and Enterprise plans), the registrations, FTDs and deposits a betting or broker platform reports back by postback.

In practice, the visit and the button click are recorded on a bridge page you host, and the button uses the funnel’s entry link, which takes the person to the channel. When they join, the tracking bot (an admin of your channel) detects it, Track4you attributes the join to the original click within the attribution window (up to 7 days after the click), and the enter_channel event goes to Meta server-side, through CAPI. Along with each event, Track4you sends the IP address, user agent and the fbp/fbc identifiers when available, which is what feeds Event Match Quality, Meta’s score for how well an event matches the person who clicked the ad.

What a CAPI call carries

A CAPI event call includes:

• the event name: a standard event like Purchase, or a custom one, such as enter_channel in a Telegram funnel;
• the moment the event actually happened (not the moment the call was sent);
• the event’s source (action_source);
• whatever user data is available: personal identifiers like email and phone are hashed with SHA-256 before sending, while IP address, user agent and the fbp/fbc cookies go unhashed;
• when the same event can also fire in the browser, a deduplication identifier (event_id), explained in event deduplication.

CAPI doesn’t replace the Pixel in most cases

On a regular website (a store, a landing page with checkout), the standard recommendation is to run the Pixel and CAPI together. The Pixel captures what it can in the browser, CAPI reinforces it with the same event (or with events the browser missed), and the two are deduplicated through the same event name and a shared event_id. Only in contexts with no browser, like a Telegram channel join, does CAPI become the only possible signal instead of a reinforcement.

On a Track4you funnel page, the advice is different: don’t install your own Meta Pixel there. Track4you’s script already sends ViewContent (page visit) and Lead (button click) to the pixel chosen in the funnel, and channel joins and exits go through CAPI. If you install your own Pixel anyway, Meta deduplicates automatically.

For the technical reference, see Meta’s Conversions API documentation, and for an in-depth explanation, the complete guide to the Facebook Conversions API. For the step-by-step setup in a Telegram funnel, read the practical guide to the Facebook Pixel and CAPI for Telegram, and for the bigger picture, the guide to tracking Telegram conversions.