Telegram Bot — conversion tracking in Telegram channel
Purpose
Telegram Bot is a type of pixel that sends notifications about conversions to a Telegram channel or group in real time. It is used to promptly track conversions (deposits, registrations, PWA installations, etc.) directly in the team's TG channel, so buyers and team leads can monitor results in real time.
Advantages:
-
✅ Instant notifications about conversions directly in Telegram
-
✅ Custom message template with macros
-
✅ Support for HTML formatting (bold, italic, etc.)
-
✅ Real-time monitoring without opening the platform
-
✅ Sending to any channel or group where the bot is an administrator
Preliminary setup: creating a bot
Before creating a Telegram Bot pixel, you need to add the bot in the Tracker → Telegram Bots section:
-
Go to Tracker → Telegram Bots
-
Click “Add Bot”
-
Specify the Name and Token of the bot (get it from @BotFather in Telegram)
-
Configure the Webhook for the bot
-
Add the bot as an administrator in the desired channel/group
The bot can also be created directly from the pixel form by clicking the “+ Bot” button next to the bot selection.
Configuring the Telegram Bot pixel
Step 1: Selecting a bot
In the “Telegram Bot” field, select the bot from the list. For administrators, the list is filtered by the selected team.
Step 2: Selecting a channel/group
In the “Channel ID” field, select the channel or group where the bot will send messages. The list of channels is loaded automatically after selecting the bot.
The bot must be an administrator of the channel/group to send messages.
Step 3: Configuring the message template
Now you can configure the pixels for the Telegram Bot.
-
Go to Pixels
-
Select the Telegram Bot type
-
Click ⋮
-
Edit
The message template defines how the notification will look in the channel. HTML markup is supported in Telegram (<b>, <i>, <code>, etc.) and macros for substituting conversion data.
Default template:
<b>{campaign.name} [{event.user_country}]</b>
Offer:{offer.name}
Revenue:{event.event_revenue}
------
FB Campaign:{event.ext_sub4} ({event.ext_utm_content})
FB Adset:{event.ext_sub5} ({event.ext_utm_term})
FB Ad:{event.ext_sub6} ({event.ext_sub1})
Example message in the channel:
💬 My Campaign [DE]
Offer: Casino Offer X
Revenue: 150
------
FB Campaign: campaign_123 (1231321584654)
FB Adset: adset_789 (12313245645465)
FB Ad: ad_012 (12333255552222)
How to insert a macro:
-
Click the button with the desired macro below the template field
-
The macro will be inserted at the current cursor position
-
The button will turn green if the macro is already used in the template
Event mapping for Telegram Bot
Mapping is configured just like for other types of pixels. You select tracker events and their corresponding events. When an event is triggered, a message is sent to the channel.
Recommended mapping:
Tracker Event | Value | When the notification will be sent |
|---|---|---|
Deposit ( |
| When a lead deposits |
Registration ( |
| When a lead registers |
PWA Install ( |
| When PWA is installed |
TG Join ( |
| When joining the TG channel |
TG Start ( |
| When the TG bot is started |
Testing the Telegram Bot pixel
To check the settings, use the “Test Telegram” action in the pixel menu (⋮):
-
Open the actions menu (⋮) for the Telegram Bot pixel
-
Select “Test Telegram”
-
The bot will send a test message with filled test data to the selected channel
-
Check the message in the channel — the data will be test data (for example,
Test Campaign,Test Offer, revenue =10.00)
Complete configuration example
Field | Value |
|---|---|
Name |
|
Network |
|
Status |
|
Bot |
|
Channel |
|
Template | (HTML template with macros) |
Event mapping:
Tracker Event | Value |
|---|---|
Deposit ( |
|
Result: with each deposit, a message arrives in the channel with the campaign name, offer, amount, and advertising campaign details.
Features of operation
-
Messages are sent via the Telegram Bot API (
sendMessagewithparse_mode: HTML) -
Asynchronous processing — events are processed through a queue, like other types of pixels
-
Sending logs are available in the pixel's “Logs” section (status, request/response)
