Skip to content
ChatterfyHelp Center
HomeGeneralCRMAI ManagerTrackerPlatformsFAQUpdate log
Main
Bot Settings
Automation & AI
CRM defaults
Flow Settings
AI Settings
Steps
Communication
Changes
Terms
Tracking
Additional
Messenger
Client card
Chat data
Chat data — main card tab
Manual — Manually Changing Lead Parameters
Custom Data — manually filling in custom fields
User Information — basic lead data
Tracker Data — traffic source data
Show Chat Events — displaying service events
Actions — exporting and clearing a conversation
Events
Users
Mailings
Analytics
  1. CRM
  2. Chat data
  3. Tracker Data — traffic source data

Tracker Data — traffic source data

The Tracker Data block in → the Chat data tab — read-only data about how the lead entered the system: which ad campaign, which source (Facebook / Google / Telegram / Custom), which domain, landing pag

Updated June 23, 20264 min
The Tracker Data block in Customer Card→ the Chat data tab — read-only data about how the lead entered the system: which ad campaign, which source (Facebook / Google / Telegram / Custom), which domain, landing page, and which tracker parameters were passed on entry.
This block appears and is populated only if the bot is connected to Tracker — Overviewand the user came through a campaign tracking link. Tracker Data is populated automatically — the operator does not enter anything here manually.
Tracker Data visibility is configured in Bot Settings → Tracker fields. This is where you define which tracker fields are displayed in the customer card and the CRM interface. If the fields are empty, the user most likely arrived organically (without a clickid and tracker parameters).


When to use this section

  1. You need to quickly understand: “where did this lead come from?”
  1. Sales adapts the approach to the traffic source — Facebook and Google audiences behave differently
  1. Support checks which landing page the user saw before registration
  1. The Buyer analyzes which campaigns generate higher-quality conversations
  1. You need to check whether the tracker parameters were passed correctly



What is displayed

Field
What it shows
Example
Campaign
Campaign name in Tracker
FB Q1 Forex India
Source
Traffic source
facebook / google / telegram / custom / organic
Domain
The domain the lead came from
promo.example.com
Landing
Landing page or transition page
default-india / custom-may-promo
Tracker parameters
Additional tracker parameters from the link
sub1, sub2, clickid, utm_campaign
Additionally, any parameters that were passed through the tracking link and enabled in the Tracker fields settings may be displayed.


Which fields to display is configured separately

The set of fields in Tracker Data is configured in Bot Settings → Tracker fields.
This is where you define:
  1. which tracker parameters are saved
  1. which fields to show to operators in CRM
  1. which values are available inside the customer card
For example:
  1. one bot shows only Campaign + Source
  1. another also shows sub1/sub2/clickid/utm_campaign
  1. affiliate teams often display broker, geo, funnel_type, traffic_type
If the required tracker field is not in Tracker Data, it does not always mean that the parameter was not passed. Its display may simply be disabled in Bot Settings → Tracker fields.


If the fields are empty

Limited Tracker Data usually means one of three things:
The lead did not come from a Tracker campaign (organic traffic).
Tracker parameters were not passed in the link.
The display of the required fields is disabled in Bot Settings → Tracker fields.


Connection with filters

Tracker Data is available as a Tracker Field parameter in:
You can filter chats by:
  1. Campaign
  1. Source
  1. Domain
  1. Landing
  1. sub1/sub2
  1. clickid
  1. utm_campaign
  1. any other tracker parameters
Examples:
  1. “only FB leads for today”
  1. “all leads with landing = crypto-may”
  1. “leads from Google without FD”
  1. “Telegram traffic + Status Manual”
This is especially useful together with saved Custom Filters — saved segments, when the team works with different traffic sources in parallel.


Where else Tracker Data is used

Tracker parameters are available inside the system through variables:
{{tracker.parameter_name}}
For example:
{{tracker.source}}
{{tracker.campaign}}
{{tracker.sub1}}
They can be used:
  1. in AI Reply — smart replies via AI
  1. in Webhook — Sending Data Out
  1. in Send message — sending a prepared message
  1. in Bot Variables — reusable values
  1. in Conditions and flow branching


Use cases

Arbitrage — audience behavior analysis

The Buyer launches two campaigns:
  1. FB-Forex
  1. Google-Forex
Opens several chats from both campaigns and compares user behavior. Notices: FB leads ask a lot of questions about registration. Google leads ask about the deposit almost immediately.
After that, changes “AI Reply — smart reply via AI” AI Reply — smart replies via AI — For Facebook, adds more onboarding information. For Google, makes replies shorter and more conversion-focused.

Sales — conversation personalization

The manager sees in Tracker Data: Landing = may-promo.
Understands that the user saw a promo with a bonus on the first deposit. The first message in the chat: “I see you came from the May promo — your first-deposit bonus is still active.” The dialogue becomes more personalized and increases the likelihood of conversion.

Team Lead — budget optimization

The Team Lead opens 20 random leads with the FD tag. Looks at Tracker Data:
  1. 80% came from FB Q1 India
  1. 20% — from Google Q1 India
Conclusion: the Facebook campaign provides higher-quality traffic. Google converts worse into FD. After that, they redistribute the budget between sources.


What to keep in mind

Tracker Data is a read-only block. You cannot change these values manually.
If tracker data is displayed incorrectly:
  1. check the tracker link
  1. check the Tracker fields settings
  1. check parameter passing


Frequently Asked Questions

Most often, yes. But it can also mean:
Tracker parameters were not passed
field display is disabled in Tracker fields
the user followed a regular Telegram link

No. Tracker Data comes automatically from Tracker and is read-only.
If you need to store your own values, use:
Custom Fields — custom fields
Custom Data — manually filling in custom fields

Yes.
Tracker fields are available in AI Reply via {{tracker.*}}. For example: {{tracker.source}}, {{tracker.sub1}}, {{tracker.landing}}.
In Webhook, via {tracker.*}. For example: {tracker.source}, {tracker.sub1}, {tracker.landing}.
You can use them in AI Reply, webhook, flow logic, and message templates.

No. Tracker Data and Custom Fields are different entities.
But you can copy values manually or automatically through a flow: {{tracker.source}} → fields.lead_source — usually via webhook or data update steps.

No.
Tracker Data shows only static attribution data: where the click came from, which campaign, which source, which landing.
Real-time user events are in the Events — Lead Event Feed.
It shows:
Page View
Click
Subscribe
Contact
Registration
FD
RD
and other events


Related

Customer Card
The client card is the right-hand panel in , which opens when you click a chat. It contains 3 tabs : Chat data (current lead parameters + actions), Events (event feed), Media (all files from the conve
Events — Lead Event Feed
The Events tab in — a real-time lead event feed . Every significant lead action (visited a landing page, subscribed to a channel, messaged the bot, registered in the affiliate program, made a deposit)
Campaigns — рекламные кампании
Именно Campaign связывает Domain, Landing, Source, Telegram, tracker-параметры, аналитику и события внутри CRM. После запуска Campaign Tracker начинает: создавать tracking-ссылки фиксировать Page View
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
Custom Filters — saved segments
The Bot Settings → Custom Filters section is where saved filters for lead segmentation are created. These are pre-built combinations of conditions that select the required audience from the entire dat
Smart Filters — advanced search in Messenger
Smart Filters are an advanced filtering mode in Messenger. With them, you can build complex lead selections using dozens of parameters: tags, steps, deposits, events, custom fields, tracking, and othe
Webhooks & API — receiving data from external sources
With a webhook, an external service can update user data, change the chat status, switch Flow steps, write values to Custom Fields, add or remove tags, and manage the conversation from an external sys
Custom Data — manually filling in custom fields
The Custom Data block in → Chat data tab — manually filling in the bot's custom fields. These are all fields from , available to operators for editing. A field can be: empty — a new lead, no data yet
Spaces — Workspaces
If you have one project and one team, you usually don’t need to configure Spaces separately: the default space is enough. When you have several business areas, create a separate Space for each. When y

Was this article helpful?

BackUser Information — basic lead dataNextShow Chat Events — displaying service events

On this page

  • When to use this section
  • What is displayed
  • Which fields to display is configured separately
  • If the fields are empty
  • Connection with filters
  • Where else Tracker Data is used
  • Use cases
  • Arbitrage — audience behavior analysis
  • Sales — conversation personalization
  • Team Lead — budget optimization
  • What to keep in mind
  • Frequently Asked Questions
  • Related