How to Send Telegram Conversion Events to Meta CAPI

Why the Meta Pixel does not work for Telegram

The Meta Pixel is a browser-based script. It fires when someone loads a webpage and executes JavaScript. Telegram is a native app, there is no webpage, no browser, and no Pixel. The moment a user taps your ad and opens Telegram, the Pixel has already lost the trail.

This means that by default, Meta sees the ad click but has no visibility into what happened next. It does not know whether the person joined your group, messaged your bot, or deposited money. So it optimises for clicks, which is the wrong signal.

What events you should send to Meta CAPI

The Conversions API lets you send server-side events to Meta after the Telegram interaction happens. The events that matter most in a Telegram funnel are:

• Telegram join, equivalent to a Lead or CompleteRegistration event
• DM received, when someone messages your bot (a stronger intent signal)
• Offer link click, when a lead clicks a tracked link inside Telegram
• Deposit or purchase, the final conversion, sent as a Purchase event with value

You do not need to send all of them at once. Start with Telegram join and purchase. Add the rest as your funnel matures.

The basic setup for sending Telegram events to CAPI

1. Capture the fbclid on your landing page before the user opens Telegram
2. Store it server-side and link it to a unique session or user identifier
3. When a Telegram event happens, retrieve the identifier for that user
4. Send the event to Meta CAPI with the original fbclid as the event match key
5. Include the event time, event name, and optionally the value and currency

The most important part is step one. If you lose the fbclid before the user enters Telegram, you cannot send meaningful events because Meta cannot attribute them to an ad.

Example event flow

A typical Meta-to-Telegram CAPI flow looks like this:

1. User clicks Meta ad, fbclid is appended to the landing page URL
2. Landing page stores the fbclid server-side, linked to a session
3. User taps a Telegram join link on that landing page
4. User joins the Telegram group or starts the bot
5. Your server detects the join and retrieves the stored fbclid
6. Your server sends a Lead event to Meta CAPI with that fbclid
7. Meta records it and attributes it to the correct campaign

Common mistakes when sending events to Meta CAPI

• Sending events without the original click ID, Meta cannot attribute them to an ad, making them nearly useless for optimisation
• Using the Pixel instead of CAPI for Telegram events, the Pixel cannot fire from inside Telegram, so this simply does not work
• Duplicate events from both Pixel and CAPI, always include a deduplication key so Meta does not count the same conversion twice
• Sending events too late, Meta's attribution window has limits; send events as close to real-time as possible
• Not including event value for purchases, without the value, Meta cannot optimise for ROAS
• Sending to the wrong pixel ID, double-check that the pixel ID in your CAPI calls matches the one in your Meta Ads account

How Tracergram solves this

Tracergram is a tool that bridges Meta ads and Telegram funnels. It handles the CAPI integration so you do not have to build the server-side infrastructure yourself. Connect your Telegram workspace and your Meta pixel, and Telegram conversion events are sent to Meta automatically with the correct attribution data.