Why deposit tracking is hard with Telegram leads
In a standard web funnel, a purchase event fires on the confirmation page and the Pixel captures it. Telegram does not have a confirmation page. Deposits typically happen days or weeks after the initial Telegram join, through a form, a payment gateway, or a manual process handled by a sales person.
By the time the deposit happens, the original ad click data has often been lost. The user is inside Telegram, there is no live browser session, and there is nothing connecting that deposit to the Meta campaign that started the journey.
What you need to track
- Campaign and ad set, which Meta campaign drove the original click
- The click ID (fbclid), Meta's identifier for that specific ad click
- Telegram identity, the username or user ID of the lead inside Telegram
- Deposit date and amount, when the deposit happened and how much
- Lead activity, whether the lead responded to follow-up before depositing
The basic deposit tracking setup
- When someone clicks your Meta ad, capture the
fbclidand UTM parameters on the landing page - Store those values server-side, linked to a unique session
- When the user joins your Telegram group or starts your bot, match their Telegram identity to the stored session data
- When a deposit is submitted, look up the stored
fbclidfor that Telegram user - Send a Purchase event to Meta CAPI with the correct
fbclid, the deposit value, and the currency
The key is maintaining the link between the Telegram user and the original click data for as long as the sales cycle lasts, days, weeks, or longer.
Example funnel
- User clicks Meta ad → landing page captures
fbclid - User joins Telegram group → system matches Telegram user ID to stored
fbclid - Sales team sends DM and qualifies the lead
- Lead submits deposit form → system retrieves stored
fbclidfor that Telegram user - Purchase event sent to Meta CAPI with value and currency
- Meta attributes the revenue to the correct campaign and ad set
Common mistakes
- Only tracking deposits in your CRM, useful internally, but if you do not send the event to Meta CAPI, the algorithm cannot learn from it
- Losing the link between Telegram user and original click, once that connection breaks, attribution is impossible
- Using UTM spreadsheets, manual tracking cannot scale and breaks whenever a data entry step is missed
- Not sending deposit value to Meta, without the value, Meta optimises for event volume, not revenue, which is a weaker signal
- Waiting too long to send the event, Meta has attribution windows; send Purchase events as soon as the deposit is confirmed
How Tracergram solves this
Tracergram maintains the connection between every visitor and their Telegram identity throughout the entire sales cycle. When a deposit is recorded, it automatically sends the Purchase event to Meta CAPI with the original click ID attached, no manual spreadsheets, no data entry errors, no lost attribution.
Start tracking Telegram deposits from Meta Ads
Know which campaigns produce paying customers, not just Telegram joins.
Start your free trial →