Author: Tracking Infrastructure Lead TG Target · S2S postback · focus: conversion signal entity, NOT affiliate program SOP.
The main thing from the article
- Postback = S2S conversion signal.
- NOT pixel — Telegram has no native pixel.
- click_id match → attribution.
- Target match rate ≥95%.
- Crypto case: match 88%→96%.
Postback flow (text diagram)
Telegram Ad click ↓ UTM / SubID captured Landing or bot (/start param) ↓ user converts (reg, FTD, deposit) CRM / backend verifies event ↓ HTTP GET/POST postback URL Tracker / MMP receives postback ↓ click_id match Conversion attributed → CPA / ROAS report
Capture layer detail — tracking glossary; window rules — attribution glossary.
S2S vs pixel in Telegram Ads stack
| Method | Signal source | Telegram Ads | Reliability |
|---|
| Browser pixel | Client-side JS | Not available in-platform | Ad-block sensitive |
| S2S postback | Server verified event | Standard stack | High if match rate ≥95% |
No Meta pixel in Telegram - UTM + SubID + postback chain is TG Target default. Analytics pillar procedural setup — analytics tracking pillar.
Postback match rate methodology (TG Target, August 2026)
Performance accounts, 30d rolling, CRM as source of truth.
| Match rate band | Accounts share | CPA report reliability | Typical root cause |
|---|
| ≥95% | 41% | High | Clean SubID + postback QA |
| 90–94% | 34% | Directional | Partial UTM loss, bot path |
| <90% | 25% | Unreliable | Broken click_id, URL errors |
Mini-case: crypto exchange EU - postback match rate fix
Licensed crypto exchange · EU · €52k/mo · FTD action · SubID via Keitaro.
| Period | CRM FTD | Postback matched | Match rate | Reported FTD CPA |
|---|
| Week 1–2 (before) | 412 | 363 | 88.1% | €143 (inflated efficiency) |
| Week 3–4 (after SubID fix) | 398 | 382 | 96.0% | €136 (true) |
Root cause: bot /start parameter did not pass SubID to CRM. Fix: single chain SubID web+bot. Match rate 88%→96%; true FTD count +5% in the report → FTD CPA corrected. Tracking setup - tracking glossary; affiliate context — affiliate marketing guide.
FAQ
What is postback in performance marketing?
Postback - cross-server (S2S) HTTP callback from advertiser/CRM to tracker/MMP upon conversion event (reg, Telegram Ads, deposit). The conversion signal object, NOT the affiliate payout process itself. The Telegram Ads stack is the primary transform transport (without an in-platform pixel).
Postback vs pixel tracking?
Pixel: browser-side JS fires on page event. Postback/S2S: server fires on verified backend event. Telegram Ads has no native Meta-style pixel — S2S postback chain is standard. Tracking glossary - UTM/SubID capture layer.
Postback flow in Telegram Ads?
Click (UTM/SubID) → landing page/bot → CRM event → hit postback URL → convert tracker attributes to click ID. Text diagram below. Analytical component - procedural SOPs; here is only a definition of the essence.
Postback vs affiliate guide mention?
Affiliate guide covers partner program setup. Postback glossary - S2S conversion signal entity with Telegram application. Cannibalization guard: link affiliate guide for partner ops, here - postback mechanics.
Match rate - what is it?
Postback match rate = attributable conversions ÷ CRM events × 100%. TG Target target value ≥95%. Below 92% → CPA/ROAS unreliable; fix SubID/UTM chain before scaling. Tracking Glossary - Capture Layer.
Typical postback parameters?
click_id/subid, event_type, payout, transaction_id, timestamp. It is necessary to map the SubID click or UTM campaign to Telegram. Gate Pre-Check - Glossary Tracking.
S2S in Telegram Ads stack (no pixel)?
The Telegram account reports only clicks/impressions. Conversions via external tracker + postback from CRM. There is no API for conversion within the platform. Attribution model - glossary of “what is attribution.”
Postback latency?
FTD/deposit postbacks may lag 4–48h (KYC). Real-time reg postbacks typical <5min. Lag affects daily CPA — use rolling windows. Glossary FTD - event lag context.
Postback red flags?
Match rate <90%; duplicate postbacks; missing click_id; HTTP 4xx on postback URL; test events in production stream. Action: SubID audit, postback log review.
Postback and FTD CPA reporting?
FTD CPA numerator depends on postback-delivered FTD count. Broken postback → understated FTD → inflated FTD CPA efficiency illusion. FTD CPA glossary - spend÷FTD formula.
The entity postback is current as of August 2026 (TG Target). Tracking capture tracking glossary; analytics SOP — analytics tracking pillar.