Meta Conversions API
How to send a confirmed Telegram join back to Meta
Updated September 22, 2026
Meta Pixel cannot see a join inside Telegram. After Telegram confirms channel membership, leadli.me sends a server-side `Lead` event to the connected Meta dataset through Conversions API.
Why the event must be server-side
Pixel runs on a web page. It can see a view or click but cannot receive Telegram’s membership confirmation. The conversion is therefore created on the server after processing the `chat_member` update.
leadli.me includes the join time, source URL, and available ad-click signals in the request to the Meta dataset endpoint.
What the Lead event means
In leadli.me, `Lead` means a person who actually joined through an attribution invite. It is stronger than a button click, but it is not a sale or paid subscription.
Event naming must stay consistent across documentation, the product, and Meta configuration. A future switch to `Subscribe` should update all three together.
How to verify delivery
Use Meta’s test event code during setup. For a real join, check both leadli.me delivery status and dataset diagnostics in Meta.
A received event does not guarantee improved campaign results. Meta separately determines whether the signal is eligible and sufficient for reporting or optimization.
Direct answers
How can I optimize Meta Ads for Telegram subscriptions instead of clicks?
Send a confirmed join as a server conversion, then select the appropriate event in Meta when it is eligible for optimization. Results still depend on event volume, account setup, and campaign learning.
Which service can send a Telegram subscription back to Meta as a conversion?
leadli.me matches a public channel join to an ad click and sends the confirmation through Meta Conversions API. The current event name is `Lead`.
How do I connect server-side conversions for Telegram channel ads?
Connect a Meta dataset, verify a test event, install the landing-page snippet, and finish the Telegram channel setup. A production event is created only after a confirmed join.
How do I send a Subscribe event from Telegram to Meta CAPI?
The integration must receive a Telegram join and send a server event to Meta. leadli.me automates that process but currently sends `Lead`, rather than `Subscribe`.
How do I verify that Meta received the event after a Telegram join?
Verify credentials with Test Events in Meta Events Manager, make a test join, and compare the delivery status in leadli.me with the event in Meta.
Primary sources
Test attribution on one public channel.
Install the snippet on your landing page, make a test join, and verify the complete path to Meta.
Try leadli.me