Direct join or join request: which one for paid Telegram traffic?
A Telegram invite link can let people in at once, or ask them to request access first. That one setting changes your join rate, what your bot is allowed to do, and who ends up in your channel.
What happens with a direct join
The person taps the link, then Join, and they are in. It is the shortest path, so it usually turns the largest share of clicks into members.
Your bot, as an admin, sees the join and the invite link that was used, so the join can be tracked. What it can't do is write to the person. On Telegram a bot may only message people who started it, and joining a channel doesn't count.
What happens with a join request
The person taps the link, then Request to join. On their side, nothing else happens until the request is approved.
On your side, the bot receives the request along with the invite link, and Telegram opens a short window: for five minutes, and until the request is approved or declined, the bot can send that person a private message. You then approve the request or decline it.
You choose when approval happens:
- Right away, for the smoothest experience.
- After a first message, for example a welcome with a button that opens the chat with your bot.
- By hand, for small private groups.
What requests give you
- A first message. Welcome people, share the rules, or ask them to tap a button. If they reply, your bot can keep talking to them later, which a channel alone never allows.
- A filter. You see who is asking before letting them in, and you can turn down obvious throwaway accounts.
- A clean count. The conversion is a person you accepted, not just a tap.
What requests cost you
An extra step loses people, especially when approval is slow. Someone who waits ten minutes for a channel they found in an ad often forgets about it. If you use requests, approve within seconds, either automatically or right after the first message.
Some people also misread the pending state and tap the link again. It does no harm, but it is one more reason to answer fast.
How each one is tracked
Both are tracked the same way: Telegram tells your bot which invite link the person used, and that link points back to the ad click.
With a direct join, the join is the conversion. With a request, decide which moment counts. The confirmed join, once the person is actually in, matches what you pay for, so it makes a good main event. The request itself can go out as a separate event if you want an earlier signal.
Which one to pick
| Pick a direct join if | Pick join requests if |
|---|---|
| You want the highest join rate | Your funnel goes on in a bot or a private chat |
| The ad already explains the offer | You want to choose who gets in |
| You only broadcast in a channel | You need that first message |
Not sure? Test both: two tracked links, the same ad, and compare the cost per first join still there after 24 hours.
With TrackJoin
In TrackJoin you choose Direct join or Join request for each link. Requests can be approved or declined from TrackJoin, and an approved request counts as a join once Telegram confirms the person is in.
Keep reading
How to track Telegram joins from Meta ads
The Meta pixel loses people at the Telegram button. How to send each confirmed channel join back to Meta as a conversion, matched to the ad.