outreach
Why FTD Tracking Links Stop Attributing Correctly
Your FTD count dropped but traffic didn't. Here's why tracking links lose attribution and how to fix the leak before you burn ad spend blind.
You check your affiliate dashboard on Monday and the FTD count looks fine. By Thursday, clicks are up 30% but deposits flatlined. Your media buyer swears the funnel didn't change. Somewhere between the click and the deposit, the tracking link lost the thread — and now you're paying for traffic you can't prove converted.
Why do FTD tracking links stop attributing correctly?
Most broken FTD attribution comes down to one of five things: cookie/session expiration (typically 24-72 hours depending on the network), a redirect chain that strips the click ID, a Telegram bot or deep link that doesn't pass the subID forward, ad platform link rewriting (Meta and Google both do this), or the lead switching devices between click and deposit. In practice, redirect-chain click ID loss and Telegram deep-link handoffs account for the majority of "phantom FTD" tickets affiliate managers deal with.
How does a redirect chain break the click ID?
Every hop in a redirect chain is a chance for the click ID (subID, clickid, gclid — whatever your network calls it) to get dropped. A typical broken chain looks like: ad → shortlink → landing page → Telegram bot → broker signup. If any one of those hops uses a 301 redirect that doesn't forward query parameters, the click ID dies right there.
The fix isn't complicated, but it requires checking every single hop, not just the first and last one:
Test the full chain manually. Click your own ad, and inspect the URL at every redirect using browser dev tools — confirm the subID is present at each step.
Use 302 redirects with explicit parameter passthrough instead of relying on the redirect service to forward params automatically.
Avoid stacking more than 2 redirects. Ad network → tracker → landing page is fine. Ad network → shortlink → cloaker → tracker → landing page is asking for data loss.
Log the click ID server-side the moment it hits your landing page, before any further redirect — so even if a later hop breaks, you already captured it.
Why does Telegram break attribution specifically?
Telegram deep links (t.me/bot?start=) can only carry one parameter — the start payload — and it has to survive being copy-pasted, opened in an in-app browser, or passed through Telegram's own link preview system. If your funnel routes a lead from an ad, through a landing page, into a Telegram bot, and then to a broker signup, that start payload is the only thing carrying attribution across the Telegram leg. Lose it there and everything downstream is unattributed, even if the lead deposits.
This is also why ad networks and Meta specifically flag or strip Telegram links more often than standard URLs — the review systems don't always parse t.me links the same way they parse web URLs. If your traffic is getting attribution gaps right around the point leads enter Telegram, it's worth reading why Telegram links get blocked by Meta ad review to rule out the link itself getting rewritten or flagged before it even reaches the user.
Related: if you're running outreach or promo through Telegram groups and losing attribution there too, ad network referral links getting blocked in Telegram groups is often the same root cause — links stripped or rewritten by the platform before the click ID survives.
What's the difference between a real FTD leak and a reporting delay?
Before you assume attribution is broken, rule out timing. Networks batch-process FTD confirmations on different schedules — some report same-day, others take 24-48 hours to reconcile with the broker's back office. A gap of a day or two is normal lag, not a leak.
Here's how to tell the difference:
Check if the gap is consistent or growing. A steady 24-hour lag is reporting delay. A gap that widens over a week points to an actual leak.
Cross-reference broker-side deposit logs against your tracker. If the broker confirms a deposit your tracker never saw, that's attribution loss, not delay.
Isolate by traffic source. If only Telegram-sourced leads show the gap and web leads don't, the leak is in the Telegram leg of your funnel, not the network.
Segment by device. Cross-device conversions (click on mobile, deposit on desktop) will always show as unattributed unless your network supports probabilistic or account-based matching.
How do you fix attribution once you've found the leak?
Once you know where the click ID is dying, the fix is usually one of these:
Switch to server-to-server (S2S) postback tracking instead of pixel-based tracking — S2S doesn't rely on the user's browser or app to fire the conversion event, so it survives Telegram in-app browsers and ad blockers.
Pass the click ID as the Telegram bot's start parameter explicitly, and have the bot log it immediately on /start, before any other interaction.
Shorten the redirect chain to the minimum number of hops needed.
Set cookie/session duration to match your actual sales cycle. If leads take 3 days to deposit but your cookie expires in 24 hours, you'll lose attribution on your slowest — often highest-value — converters.
If your funnel involves managing hundreds of leads across Telegram chats before they ever reach the broker, tracking who came from which campaign gets messy fast once you're doing it manually. Segmenting Telegram leads by deposit status in a spreadsheet is a stopgap, but it doesn't fix the underlying click ID problem — it just helps you see the damage.
Can a CRM prevent this instead of just reporting on it?
CRMChat lets you tag and segment leads by source and pipeline stage directly inside Telegram, so even when a network-side click ID gets lost, you still have a record of which campaign, sequence, or account brought the lead in. That doesn't replace S2S tracking, but it gives you a second, independent attribution trail when the primary one drops. CRMChat also includes an API for teams that want to sync deposit and conversion events from their broker or tracker back into the CRM pipeline automatically — check the CRMChat API docs if you're building that connection.
If your outreach accounts are the ones driving leads into Telegram in the first place, keep in mind that unwarmed accounts getting restricted mid-campaign will also create attribution gaps that look like tracking bugs but are actually just missing traffic. Check your account health before you spend a week debugging a link that was never broken.
Quick checklist before you blame the network
Confirm the click ID survives every hop in your redirect chain, tested manually.
Check whether the gap is a consistent reporting delay or a growing leak.
Isolate whether the leak is specific to Telegram-sourced traffic.
Verify your cookie/session window matches your real deposit timeline.
Confirm your Telegram bot logs the start parameter immediately, before any redirect.
Cross-check broker deposit logs against tracker data weekly, not just when something looks wrong.
