Overview
Both tracking methods end with the fan sending a message to the explicitly selected Secretary profile. Direct Profile minimizes steps; Start With Bot first records a stable Telegram identity through a signed Start payload, then a Bot Flow can guide that fan to the selected profile DM.
- Choose the lower-friction or stronger identity path intentionally.
- Understand the fan action required to complete attribution.
- Keep every link tied to one exact Secretary destination.
Before you start
- Select the exact Telegram account that should own the tracking or community action.
- Use public Telegram usernames for profiles and bots that fans must open.
- Test the complete fan journey with a separate Telegram account before distributing a link.
Step by step
- Select the Telegram account that should own the tracking link.
- Choose Direct Profile when you want the public link to open that profile DM with a pre-filled marked message.
- Choose Start With Bot when you want a signed Start event to identify the fan before a Bot Flow directs them onward.
- For Start With Bot, select the exact Secretary profile that the flow button must open.
- Test the journey and send the final DM from the same Telegram account used at the beginning.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Direct Profile | Attribution can complete only when the fan sends the pre-filled DM while its invisible click marker is still present. |
| Start With Bot | The signed Start event stores the fan's stable Telegram user identity before the later profile handoff. |
| Identity bridge | The standalone bot connects identity and routing; the selected Secretary profile remains the final conversation destination. |
| No guaranteed conversion | The fan must still complete every visible Telegram step, including opening the selected profile and sending a DM. |
Verify the result
- The public link opens the exact Telegram destination configured for the selected account.
- A test fan completes every required Telegram action before attribution is expected.
- Campaign metrics are read with the same date range and manual spend assumptions.
Troubleshooting
| If you see this | What to check |
|---|---|
| A tracking link records clicks but no conversation | Complete the selected Direct Profile or Start With Bot journey, including the final fan message to the exact Secretary profile. |
| Revenue is not attributed | Check the attribution window, selected destination profile, fan identity, and whether a qualifying purchase occurred in that conversation. |
| A public growth page shows no data | Confirm the workspace opted in where required and that qualifying activity occurred in the selected period. |
Best practice
Create one clearly named link per source or campaign and test its full Telegram journey before comparing traffic quality.