Meta Conversions API for Telegram
Show Meta which ads bring people to your Telegram channel.
The Meta Pixel runs in the visitor's browser, so privacy settings and ad blockers often stop it. Telegram Tracker sets up the Pixel and the Conversions API together, and reports every request to join your channel against the ad that sent it.
- Self-service setup in minutes
- Everyone who asks is approved
- Personal data removed after 8 days
See which ads bring people to Telegram
Telegram does not report joins back to Meta, so Meta only knows someone clicked. Telegram Tracker closes that gap.
Attribute every join request
Each request to join your channel is matched to the campaign, ad set and ad that sent the visitor.
A personal invite link per visitor
The Join button creates one link for each visitor, so a request can be traced back to the click behind it.
Pixel and Conversions API together
The browser Pixel and our server send the same events with one shared ID, so Meta keeps one copy.
Subscribe sent to Meta
When the join request arrives, a Subscribe event goes to Meta with the ad information attached.
Duplicates and suspected bots flagged
Repeat requests, shared links and crawlers are kept out of Meta events. Nobody is refused entry.
Live numbers per ad
See visitors, Join taps and requests to join by campaign and ad, as they happen.
From one tap to one join request
Ad click recorded
The visitor taps your ad and lands on your page. We record the campaign and ad they came from.
Landing page, Pixel and server events
PageView, ViewContent and Lead are sent from the browser Pixel and from our server.
A personal invite link
The Join button gives that visitor an invite link of their own for your channel.
Request approved, Subscribe sent
Their join request is approved and a Subscribe event goes to Meta. Subscribe means requested to join; Telegram confirms the join separately.
Everything in one dashboard
Numbers keep requests and confirmed joins apart, and flags are evidence, never proof about a person.
Funnel per campaign and ad
Visitors, Join taps, join requests and joins confirmed by Telegram, by campaign, ad set and ad.
Live activity feed
Each visit and join request as it happens, with its attribution state.
Duplicates and suspected bots flagged
Repeat requests, shared links and link-preview crawlers are kept out of Meta events. A flag is our evidence, not proof about a person.
Money protected (estimate)
What duplicate requests would have cost you at your own cost per join. An estimate, not a measurement.
Auto-approve and welcome message
Everyone who asks is approved, after a delay you choose, with an optional welcome message.
Bots saved to your account
Add a bot once and connect it to any of your workspaces.
Three landing templates
Text-only templates with your accent colour, or a direct link straight to Telegram.
Team access and CSV export
Invite admins and view-only teammates, and export visits and requests as CSV.
Pixel and Conversions API, one event ID
PageView, ViewContent and Lead go from the browser and from our server with the same event ID. Subscribe is sent from our server, and every retry reuses its ID.
Test mode
Send events with a test code to Meta's Test Events window before you go live.
8-day personal data retention
Visitor IPs and identifiers are removed after 8 days. Tokens are stored encrypted.
Meta Pixel alone vs Telegram Tracker
| Capability | Meta Pixel alone | Telegram Tracker |
|---|---|---|
| Server-side events | Not included | Included |
| A personal invite link per visitor | Not included | Included |
| Ad-level attribution of join requests | Not included | Included |
| Duplicate and suspected bot flags | Not included | Included |
| Landing page included | Not included | Included |
Questions
Do I need to write any code?
No. Connect a Telegram bot, add your channel, connect your Meta dataset, and publish a page. Point your ad at the page address.
How long does setup take?
Setup is self-service and usually takes minutes. There is no call to book and nobody to message first.
Does it refuse anyone who asks to join?
No. Everyone is approved. Duplicates, shared links and suspected bots only stop the Meta event.
Can it prove every member is a real person?
No tool can. We flag what our evidence shows, such as a duplicate request or a known crawler, and keep it out of Meta events. Flags are evidence, not proof.
What does the bot need in my channel?
Administrator rights with "Invite users via link", so it can create join links and approve requests.
What does Subscribe mean?
Someone asked to join. Telegram confirms a join separately, and the dashboard shows requests and confirmed joins as two numbers.
How long do you keep visitor data?
Personal data such as IP addresses and identifiers is removed after 8 days. Bot and Meta tokens are stored encrypted.
Can I test before going live?
Yes. Test mode sends events with a test code to Meta's Test Events window.
Start with one channel
Create an account, connect your bot and publish your first page.