Tracker — Overview
When a lead follows a tracking link, the module uses clickid to link the click to subsequent events (for example, registration and a deposit). The data is matched with the CRM: the operator sees the l
When a lead follows a tracking link, the module uses clickid to link the click to subsequent events (for example, registration and a deposit). The data is matched with the CRM: the operator sees the lead’s source and conversions. Tracker is usually used for paid traffic in Telegram.
When to open this section
- You need click tagging and an “ad → subscription or chat → conversions” link to the campaign, creative, and source.
- You need to receive partner program postbacks and match them to leads.
- You need to split campaigns among buyers and see the result for each employee.
- You plan to use your own domains and landing pages for redirects to Telegram.
- You need to send conversions to ad accounts or debug incoming and outgoing events using logs.
What’s inside
Basic flow: domain → landing page → bot or channel in Telegram → partner program. Connect the domain through Cloudflare and add it to Chatterfy. Build the redirect page on the landing page (Default or Custom). In the campaign, set the domain, landing page, and source binding; configure link tagging parameters in the campaign, and traffic sources in the Sources section. The partner program sends a postback to Chatterfy; the event is matched to the lead by clickid.
Section | Purpose | When to open |
|---|---|---|
Dashboards | Summary metrics and charts from click to repeat deposit | Daily KPI monitoring without deep segmentation |
Campaigns | Linking the domain, landing page, source, and Telegram entry point to a bot or channel; filters, link parameters, automatic actions | Setting up and editing a traffic run |
Sources | Facebook, Google, Telegram, and Custom profiles for campaigns | Creating or checking the provider before and after launch |
Domains | Custom domains for tracking links and landing pages | Initial connection or domain change |
Landings | Pages between ads and Telegram: Default or Custom (ZIP) | New or replacement landing page |
Analytics | Metrics table with filters, grouping, and CSV export | Funnel analysis and report preparation |
Integrations | Incoming postbacks: templates and custom schemas by clickid | Connecting an affiliate program |
Buyers | Buyer and Buyer Team Lead roles | Assign a Buyer Team Lead to a specific employee |
Proxy | Proxy for server-side event sending to external sources | Configuring S2S and reducing blocks |
Logs | Real-time log of incoming postbacks and outgoing sends | Debugging postbacks and conversions |
Sections at a glance
Expand a section to read the description and go to the detailed article.
Dashboards — сводная аналитика
Key metrics and funnel charts on one screen. Use this for quick trend checks; detailed breakdown is in Analytics.
Learn more — Dashboards — Summary Analytics
Campaigns — рекламные кампании
The central Tracker object: domain, landing page, source, transition to Telegram, parameters, and traffic restrictions.
Learn more — Campaigns — advertising campaigns
Sources — источники трафика
Provider profiles and fields for passing events back. A campaign references the required profile; creation and editing are in this section, not only inside the campaign card.
Learn more — Sources — Traffic Sources
Domains — собственные домены
Connecting a domain via Cloudflare for links and standard landing pages.
Learn more — Domains — custom domains
Landings — лендинги перехода в Telegram
Default template with settings or uploading a Custom template as a ZIP.
Learn more — Landings — Telegram redirect landing pages
Analytics — детальная таблица
All Tracker metrics with filters and export to CSV.
Learn more — Analytics — detailed table
Integrations — партнёрские программы
Receiving postbacks using ready-made templates or a custom configuration.
Learn more — Integrations — Partner Programs
Buyers — байеры и тимлиды
Separating Buyer and Buyer Team Lead access to campaigns and reports.
Learn more — Buyers — Buyers and Team Leads
Proxy — прокси для S2S
Proxy servers for server-side sending of conversions to external networks.
Learn more — Proxy — proxy for S2S
Logs — журнал событий
Incoming requests from affiliate networks and outgoing sending to ad sources; troubleshooting errors and discrepancies.
Learn more — Logs — event logs
Where to start
Just getting to know the module
Need to launch from scratch
Preparing a domain
Need a landing page
Connecting an affiliate program
The postback doesn’t arrive or conversions don’t match
Frequently asked questions
Related
Was this article helpful?




