TG-Staff 团队 avatar TG-Staff 团队

Cryptocurrency Split Link Guide: Achieving Web3 Marketing Precision Tracking and Compliant Traffic with Telegram Bot

Telegram Shunt Link Crypto Web3

Cryptocurrency Diversion Link Guide: How to Use Telegram Bot for Web3 Marketing Precision Tracking and Compliant Traffic

Running community operations and customer service on Telegram is almost a standard move for cryptocurrency projects. But when you’re simultaneously running ads or posting activity links on Twitter, Google Ads, Mirror, CoinMarketCap, and other channels, a core issue remains unavoidable: Where did the user come from?

Telegram’s native mechanism cannot pass UTM parameters or channel sources. Traditional short link tools (like Bitly) only record click counts and cannot continue tracking after the user jumps to your Bot. Worse, once a user enters the Bot conversation, subsequent actions like inquiries, orders, whitelist applications become completely disconnected from the initial ad click—this is the classic “attribution black hole.”

This article will break down from a practical perspective how cryptocurrency diversion links work, how they differ from ordinary short links, and how to use them to build a complete Web3 marketing conversion funnel from ad click to Bot conversation to human agent handoff. We’ll also cover compliance and internal control issues that crypto projects care about most, such as preventing agents from accidentally sending wallet addresses or sensitive information.


Three Major Challenges of Traditional Advertising: Attribution Black Hole, Bot Jump Breakage, Compliance Blind Spots

Imagine a typical DeFi protocol running ads on the following channels simultaneously:

  • KOL promotion posts on Twitter
  • Brand keyword ads on Google Ads
  • Banner ads on CoinMarketCap
  • “Join Community” button on the project website

Each channel links directly to the Telegram Bot’s t.me/your_bot?start=xxx link. What happens?

  1. Attribution Black Hole: You can only see the Bot’s start parameter but can’t tell if the user came from Twitter or Google. The start parameter can only be manually set as a static identifier and cannot carry dynamic UTM information like source, medium, campaign.
  2. Bot Jump Breakage: User clicks link → jumps to Telegram client → opens Bot conversation → clicks Start button. Throughout this process, the user’s device type, IP location, and browser information are all lost. You can’t tell if it’s an iOS or Android user, or if they’re on desktop or mobile.
  3. Compliance Blind Spots: In crypto projects, customer service conversations often involve sensitive content like wallet addresses, transfer information, and contract addresses. If an agent mistakenly or maliciously sends the wrong payment address, it’s almost impossible for the project to trace back. Worse, if a user enters the Bot through a certain channel and is then directed to a phishing address, responsibility attribution becomes very blurred.

The design purpose of diversion links is to solve the above three problems. Here’s how it works:

  1. The user clicks a short link in https://app.tg-staff.com/{code} format on an ad platform or social media.
  2. Before the redirect, the system automatically captures the user’s IP address, browser UA (device type, operating system), Referrer (source page), and UTM parameters in the URL.
  3. Then, the link automatically redirects to your designated Telegram Bot, and the user enters the Bot conversation.
  4. The Bot automatically replies with a welcome message or menu, while passing the captured visitor information (channel source, device, IP, etc.) to the backend.
  5. If the user needs a human agent, the system assigns the conversation to an online agent, who can see the user’s complete source information in the web console.

This way, the full-chain data from “user clicks ad” to “human agent receives” is connected. No more attribution black holes or jump breakage.


Ordinary short links (like Bitly, Rebrandly) have a core function: shorten URL + count clicks. They cannot do the following:

  • Pass attribution parameters: You cannot attach UTM parameters to the short link and then parse source=twitter or medium=cpc in the Bot backend.
  • Auto-redirect to Bot and capture user info: Ordinary short links redirect to t.me/your_bot and then lose user information. They don’t capture IP, UA, etc., before redirecting.

Telegram diversion links, on the other hand, are short link services specifically designed for the Telegram Bot ecosystem. Their key differences:

FeatureOrdinary Short Links (Bitly, etc.)Telegram Diversion Links
Shorten URL
Click stats
Pass UTM parameters
Capture visitor IP & device
Auto-redirect to Bot and pass parametersRedirect only, no passingRedirect + pass attribution data
Data integration with customer service system✅ (source visible in conversation page)
Used for ad attribution analysisOnly basic click dataCan be linked to subsequent service conversations and conversions

So, if you only need to shorten a link to send to users, ordinary short links are enough. But if you need to know which channel the user came from, what device they’re using, which region they’re in, and associate this data with subsequent customer service conversations, diversion links are the better choice.


Suppose you run an NFT minting project and are promoting through the following channels:

  • Twitter Ads: Tweets with “Mint Whitelist Application” links
  • Google Ads: Search ads pointing to “Join Community for Latest Updates”
  • Project Website: “Contact Us” button in the bottom right corner

You want to track conversion performance for each channel and, during peak consultation times, automatically assign conversations to online agents. Here’s a three-step actionable plan.

In the TG-Staff console, generate a separate diversion link for each channel and manually add UTM parameters. For example:

  • Twitter Ads: https://app.tg-staff.com/twitter_nft?utm_source=twitter&utm_medium=cpc&utm_campaign=nft_mint_q1
  • Google Ads: https://app.tg-staff.com/google_nft?utm_source=google&utm_medium=cpc&utm_campaign=nft_mint_q1
  • Website Button: https://app.tg-staff.com/website_contact?utm_source=website&utm_medium=button&utm_campaign=contact_us

Note: UTM parameters can be customized, but it’s recommended to follow standard naming conventions (source, medium, campaign, term, content) for easy unified processing in analytics tools later.

Tip: Split links work better with UTM parameters

Naming conventions matter. It’s recommended to standardize UTM naming rules within your team, for example, use lowercase letters for utm_source and name utm_campaign by quarter or campaign. This way, after exporting data, you can directly analyze it using pivot tables in Excel or Google Sheets without manual cleaning.

After a user clicks any of the above links, three things happen:

  1. Before redirecting, the diversion link system captures the user’s IP, browser UA, Referrer, and all UTM parameters from the URL.
  2. The system automatically redirects to your Telegram Bot (the Bot project you configured in TG-Staff in advance).
  3. The Bot sends an automatic welcome message, for example: “Welcome to the XX NFT project! Click the menu below to view whitelist application conditions.”

At the same time, in the conversation page of the TG-Staff backend, the agent can see the user’s “Source” field, displayed as twitter / cpc / nft_mint_q1, as well as the device type (e.g., Chrome on Windows) and IP location.

Step 3: Combine with Conversation Routing Rules to Assign Users to Online Agents

When a user clicks the “Customer Service” button in the Bot menu or triggers a process requiring human intervention, TG-Staff will assign the conversation to an agent based on your preset Conversation Routing Rules.

There are two routing rule modes:

  • Round Robin (default): Polls agents with permissions in order, suitable for teams with a fixed number of agents and a steady work pace.
  • Online First: Prioritizes assigning to currently online agents; if all are offline, falls back to round robin. Suitable for scenarios with fluctuating inquiry volume, such as during peak whitelist application periods.

It is recommended to enable “Online First” mode during events. Combined with diversion link channel tracking, you can see in real time: Which channel has the highest inquiry volume? Which channel has the best conversion rate? This allows you to quickly adjust ad budget allocation.


In customer service conversations for encryption projects, information such as wallet addresses, contract addresses, and transfer amounts appear frequently. If an agent mistakenly or maliciously sends an incorrect payment address, the consequences could be user asset loss and project reputation damage.

Wallet Address Monitoring: Prevent Agents from Mistakenly or Illegally Sending Payment Addresses

TG-Staff Professional Edition provides Content Risk Control (Internal Control Management) features. You can configure keywords to monitor in risk phrases, for example:

  • Specific TRC20/USDT payment addresses (e.g., TXYZ1234...)
  • Common address prefixes or regex patterns (e.g., Ethereum addresses starting with 0x, TRC20 addresses starting with T)
  • Specific contract address fragments

When an agent sends a message containing these keywords in the chat input box, the system triggers a confirmation pop-up, asking the agent to confirm whether to send. If a high-risk phrase is matched (e.g., an unauthorized wallet address), the system can directly block the message.

Risk Phrase Audit: Trace Problem Conversations and Agents via Trigger Records

All triggered content risk control events are recorded in TG-Staff’s audit log. You can view:

  • Which agent triggered the event
  • The conversation associated with the trigger (linked to the user)
  • The time of the trigger
  • The specific content of the risk phrase

This means that in case of a dispute (e.g., a user complains about receiving an incorrect payment address), you can quickly locate the agent who handled the conversation, the chat history, and the trigger record as evidence for compliance audits.

Best Practice: It is recommended to add all official payment addresses and commonly used contract addresses to a “whitelist” or “allowlist” before project launch, while adding unauthorized addresses to risk phrases. This ensures agents can only send approved addresses, reducing risk at the source.


Beyond basic channel attribution, diversion links can be used in more creative ways.

1. Multi-Language Campaign Diversion

If your project targets English, Chinese, and Korean users simultaneously, you can add ?lang=en or ?lang=zh parameters to the diversion link. Upon receiving the parameter, the Bot automatically replies with a welcome message in the corresponding language. Users do not need to manually select a language, resulting in a smoother experience.

2. Airdrop/Whitelist Campaign Tracking

In airdrop campaigns, generate unique diversion links for each KOL (e.g., ?ref=kolid123). When a user enters the Bot via that link and completes the whitelist application, the backend can record the user’s source KOL. After the campaign, settle commissions based on the number of valid applications brought by each KOL.

3. Community Referral Effect Attribution

In “Invite Friends” links shared within the community, use diversion links as well. The inviter’s UID can be encoded in a URL parameter. When the invitee completes registration or joins the group, the system can automatically record the referral relationship for subsequent point rewards or leaderboards.

Limitations of Diversion Links

While diversion links are powerful, they rely on users actively clicking and successfully redirecting. If the redirection fails due to network issues, Telegram client not being installed, or the bot’s quiet period (no interaction within 24 hours), this data will be lost. It is recommended to combine with the bot’s start parameter for dual recording and use Webhook callbacks for data completion.


Implementation Tips and Common Pitfalls

Correctly Configure UTM Parameters

  • Use lowercase for all parameters to avoid case sensitivity issues that can cause data grouping errors.
  • utm_source Fill in the channel name (e.g., twitter, google, telegram_group).
  • utm_medium Fill in the medium (e.g., cpc, social, email, organic).
  • utm_campaign Fill in the campaign name (e.g., nft_mint_q1, ambassador_program).
  • Avoid using Chinese characters or special characters, as some ad platforms may not parse them correctly.
  • Telegram and some ad platforms have strict blocking policies for t.me links. Using a diversion link (app.tg-staff.com domain) can reduce the chance of being blocked because it is a separate domain not on Telegram’s blocklist.
  • If the ad platform requires HTTPS links, ensure your diversion link has an SSL certificate configured (TG-Staff supports this by default).

Handling Bot Quiet Period User Loss

Telegram Bot has a “quiet period” mechanism: if a user has not interacted with the bot within 24 hours, the bot cannot send messages proactively. This means that after a user clicks the diversion link, if the bot does not respond promptly with a welcome message, the user may be lost.

Solution: Ensure your bot sends a welcome message immediately when a user first enters (e.g., “Thanks for following! Please click the menu below to start.”). If you use TG-Staff’s visual command flow, you can set an “auto-reply” node at the first step to ensure zero-delay response.


FAQ

Q: What user information can diversion links track?

A: Diversion links can capture the user’s IP address (for location), browser User-Agent (device type, OS, browser), Referrer (source page), and UTM parameters in the URL (e.g., utm_source, utm_medium, utm_campaign). This information is bound to the user’s Telegram account and displayed to agents in the chat session page.

Q: Can the free or standard plan use diversion links?

A: TG-Staff’s Standard and above plans support the diversion link feature. The free trial period (3 days) also allows you to experience this feature. For specific pricing and feature differences, please check the official pricing page.

Q: Do diversion links support multilingual bots?

A: Yes. You can customize parameters in the diversion link URL (e.g., ?lang=en) and then return responses in different languages based on the parameter value in the bot’s visual command flow. TG-Staff also provides automatic translation (Standard plan includes AI translation, Professional plan additionally supports Google Professional Translation and DeepL Professional Translation), further reducing the barrier for multilingual operations.

Q: How to prevent diversion links from being abused?

A: Diversion links themselves do not provide anti-abuse mechanisms, but you can reduce risks by: 1) Setting verification steps in the bot flow (e.g., captcha, email verification); 2) Using TG-Staff’s session routing rules to assign sessions from abnormal sources to specific agent groups; 3) Regularly reviewing diversion link click data, and when abnormal IP ranges or high-frequency clicking are detected, replace the link or adjust ad targeting strategies promptly.

Q: What plan is required for wallet address monitoring?

A: Wallet address monitoring is a content moderation (internal control) feature of TG-Staff Professional plan. The Standard plan does not include this feature. The Professional plan supports configuring risk phrases, confirmation pop-ups, blocking sends, and full trigger record auditing. If you need to manage multiple agents and involve sensitive asset information, upgrading to the Professional plan is recommended.


Next Steps

If you want to implement diversion links, channel attribution, and compliance risk control in your crypto project, follow these steps:

  1. Register for TG-Staff free trial (3 days): Visit https://app.tg-staff.com/ to create an account.
  2. Connect your Telegram Bot: Add the Bot Token in the console and configure basic settings.
  3. Generate diversion links: Create links in the “Diversion Links” module and add UTM parameters.
  4. Configure session routing rules: Choose “Round Robin” or “Online First” based on your team’s agent count and online hours.
  5. Enable content moderation (Professional): Add wallet addresses or sensitive words, and configure trigger rules.

For detailed configuration documentation, refer to: https://docs.tg-staff.com/

If you have specific scenarios to consult, feel free to contact the official bot: @tgstaff_robot