Meta Conversions API for Telegram: Send Joins and Deposits Back to Meta

Conversions Meta cannot observe

Meta's delivery system relies on feedback. It serves the ad, observes the result and adjusts delivery accordingly. In a Telegram funnel the result happens outside Meta's view, so the feedback never arrives. A campaign without conversion data cannot improve its targeting, regardless of how long it runs.

What the Conversions API changes

The Conversions API (CAPI) is a server-to-server channel. Instead of relying on a browser script, a server posts events directly to your Meta dataset. This makes it possible to report events that happen inside Telegram, and those events are not affected by ad blockers, iOS tracking restrictions or cookie loss.

Standard event names. Joins are sent as CompleteRegistration, DMs as Contact, and deposits and Stars payments as Purchase, so Meta can optimise for them. The mapping can be edited per workspace.
Click identity. The fbc parameter is rebuilt from the original fbclid, which links the event to the ad.
Match parameters. Hashed email, phone and a hashed Telegram user ID are included when available, together with client IP address and user agent.
Deduplication. Every event carries a stable event ID, so retries and repeated actions are not counted twice.

Illustrative example: what Meta receives

A Purchase event with a value of 120 and currency EUR, the tracking link as the event source, fbc from the original click, an external ID derived from the Telegram account, and a source_event field showing that it originated as a Deposit in your funnel. Test event codes let you confirm the event in Events Manager before any campaign relies on it.

Benefits for advertisers

Campaigns optimised for members and depositors instead of clicks
Lookalike audiences built from people who converted
Conversion columns in Ads Manager that reflect Telegram outcomes
Reporting that continues to work when browsers block third-party tracking

Frequently asked

What do I need from Meta?

A dataset ID and a Conversions API access token, both available in Events Manager at no cost.

Can I keep my website pixel?

Yes. The pixel and the Conversions API can run together. Tellmetric's event IDs allow Meta to deduplicate any event reported by both.

How does Meta assess my data quality?

Largely by the match parameters each event carries. The match quality panel shows your coverage of fbc, email, phone and external ID, so you can see where to improve.

Can I rename the events?

Yes. Each workspace can map internal events to any Meta standard event, for example Joiner to Lead instead of CompleteRegistration.

Meta Conversions API for Telegram funnels