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
Events
Users
Mailings
Analytics
Analytics
Chats — conversation analytics
Steps Conversion — funnel by flow steps
Billing — bot expenses
Tracker Conversion — conversion from conversation to RD
  1. CRM
  2. Analytics
  3. Tracker Conversion — conversion from conversation to RD

Tracker Conversion — conversion from conversation to RD

The Tracker tab in — conversions from dialogs to affiliate events from . Shows the lead's entire journey: from the first message to the bot (Dialog) to registration in the affiliate program (Registrat

Updated August 30, 20266 min
The Tracker tab in Analytics — conversions from dialogs to affiliate events from Glossary. Shows the lead's entire journey: from the first message to the bot (Dialog) to registration in the affiliate program (Registration), first deposit (FD), and repeat deposits (RD).
10 metrics that show where conversion is lost in the funnel and how high-quality the traffic is. Key analytics for a media buyer evaluating campaign effectiveness.
This is analytics for a specific bot
— it differs from similar metrics in the general module Analytics — detailed table, where the same events are viewed through the lens of all campaigns and sources. Here, it is about what happens after the lead reaches this bot.



When to open this section

The Buyer launched a campaign, a week has passed — assess traffic quality
The Sales team wants to understand how many leads actually reach a deal
Quarterly review — this bot's conversions over 90 days
Before / after flow optimization — was there a drop?
Comparing “organic vs paid” by splitting by the Tracker Field in User filtering — 11 parameters



10 metrics

Metric
What it counts
Ideal value*
Dialogs
Number of dialogs with the bot during the period
The higher, the better
Dia → Reg
Conversion from dialog to registration (%)
30–50% is good, 50%+ is excellent
Registrations
Absolute number of registrations
—
Reg → FD
Conversion from registration to first deposit
20–40%
Dia → FD
Direct conversion from dialogue to FD
5–15%
FD
Absolute number of first deposits
—
FD → Uniq RD
Percentage of FD leads who made at least one RD
30%+
Unique RD
Unique repeat payers
—
FD → RD
How many RDs per FD lead on average
1.5+ is good
RD
Total number of repeat deposits (including repeats by the same lead)
—
The numbers in the “Ideal value” column are for arbitrage traffic to financial offers.
For e-commerce, sales services, and info businesses, the metrics can be completely different. Your own benchmark — compare only against your own previous periods within your business, not against these numbers as an absolute standard.



Charts

Each metric is displayed on a separate chart with daily dynamics. This allows you to:
See the trend over the period — growth, decline, stagnation.
Find anomalies — sharp spikes or drops.
Compare waves across different metrics — for example, Dialogs dropped, but Registrations are holding steady.



Period

The same options as in “Chats — dialog analytics” Chats — conversation analytics —
Today/7 days/14 days/30 days/90 days
Custom range via the calendar
RD events arrive with a long delay
— for quarterly RD analysis, you need at least a 90-day period. If you look at 7 days, RD will almost certainly be understated, so do not draw conclusions based on it.



How it differs from Tracker → Analytics

Where
What it shows
Analysis angle
Analytics → Tracker (this section)
Conversions for this bot
“What happens to leads in bot X”
Analytics — detailed table
Conversions for all campaigns / sources / landing pages
“Which ads bring quality traffic”
Use both sections:
Analytics → Tracker — to optimize the funnel inside the bot (flow / AI / steps).
Tracker → Analytics — to optimize traffic (ads / landing pages / sources).



What each metric reveals

Low Dia → Reg (< 20%)

Leads reach the bot but do not register.
Possible reasons:
AI Reply does a poor job of qualifying them.
The offer is unclear in the first messages.
The leads are not targeted (a poor campaign).
Solution: strengthen AI Reply — smart replies via AIGoal/Requirements, check the landing page, add a clarifying step to the flow.



Low Reg → FD (< 10%)

They register but do not make deposits.
Possible reasons:
Issues in the affiliate program itself — KYC, minimum deposit amount.
A long gap between registration and the offer — the lead has gone cold.
No push messages after registration.
Solution: check the partner’s terms, set up push messages immediately after Registration. Push Messages — Re-engaging Silent Users.



Low FD → RD (< 1.2)

Leads make the first deposit but do not make repeat deposits.
Possible reasons:
Weak retention in the affiliate program (a poor product).
Insufficient follow-up in chat after FD.
No reactivation program for FD leads.
Solution: set up Push Messages — Re-engaging Silent Users7–14 days after FD, add a personal message from a manager, check the affiliate program terms.



Use cases

Campaign evaluation after 30 days

Period: 30 days after campaign launch.
Metric
Value
Assessment
Dialogs
1500
—
Dia → Reg
35%
Excellent
Reg → FD
28%
Good
Dia → FD
9.8%
Good
FD → Uniq RD
18%
Low — retention needed
Conclusion: traffic is high-quality, the funnel from registration to FD works, but retention is weak. Action — configure Push Messages for the FD segment.



Failure diagnosis

Compare “last week vs this week”:
Dialogs are the same, ~500.
Registrations dropped from 200 to 100.
Dia → Reg = 20% instead of 40%.
The campaign did not change → the problem is in the bot.
Action: open several leads from this week → Show Chat Events — displaying service events → you see mass Error events at the Qualify step. AI Reply broke — after a model or prompt update.



A/B test for retention via Push Messages

Old flow: FD → Uniq RD = 15%.
Launched new Push Messages 7 days after FD.
After a month: FD → Uniq RD = 26%. Growth +73%.
Action: save the new flow as the main one and disable the old one.



What to keep in mind

Events are delayed.
Postbacks from partners arrive not instantly:
Minutes — for active partners.
Hours — the usual delay.
24 hours or more — some partners with manual moderation.
Today's FD/RD may be displayed incompletely. For an accurate analysis of a specific day — check 24–48 hours after the day ends. Do not make urgent conclusions like “the campaign failed today” based on today's numbers.
Organic traffic is counted.
Leads without clickid are also included in these metrics if they reached Subscribe / Contact / Registration. Their events are not tied to a campaign, but they are visible in the bot.
If you need to separate organic from paid traffic — use a filter in User filtering — 11 parameterswith the Tracker parameter Field source = empty (for organic) or source = "facebook" (for a specific campaign).



FAQ

This section (Analytics → Tracker) — funnel analysis inside a single bot. What happens to leads after they get into this bot: Dia → Reg → FD → RD.
The Analytics — detailed table section is analysis by campaigns, sources, and landing pages. Which ads bring high-quality traffic.
Use both: the first to fix the flow, the second to fix traffic.

Yes. Leads without clickid (who came via Telegram search, a direct link, or a contact shared by an acquaintance) are included in the metrics if they have Subscribe / Contact / Registration events. To separate them — use a filter in User filtering — 11 parameters with TrackerField source = empty.

All events or only those from postback? Analytics includes all events regardless of how they are sent. Events sent manually via Send event — manual event triggering, are included in the metrics just like events from postback and integrations.

Checklist of reasons:
Partner conditions became stricter— new KYC requirements, a higher minimum deposit amount.
Long gap between Registration and the deposit offer— the lead cooled off during that time.
No pushes after Registration— the lead registered and forgot; they won’t come back without a reminder.
Technical problems on the partner’s side— deposits do not go through, leads drop off.
Check in this order: partner → timeline inside the flow → messages after Registration.

Depends on the task:
Unique RD(how many leads make repeats) — for evaluating retention. “What percentage of FD leads returned?”
RD(total number of repeats) — for revenue forecasting. “How many repeat deposits will we get in total this month?”
If both metrics are growing, great. If RD is growing but Unique RD stays flat, a few leads are making many repeats while the rest are silent (concentration in a narrow VIP group).

Yes. For statistically significant metrics, you need at least 7 daysfor Dia / Reg / FD. For RD —at least 30 days, preferably 90, due to postback delays and because a lead can make a repeat deposit weeks after the first one.

Related

Analytics
The Analytics section is analytics for a specific bot in Chatterfy . Four tabs answer four different questions: how many leads are coming in (Chats), where they drop off in the funnel (Steps Conversio
Chats — conversation analytics
The Chats tab in the — is the main analytics view for the number of bot conversations. Here you can see: how many users messaged the bot how activity changes by day whether leads return how effectivel
Steps Conversion — funnel by flow steps
Steps Conversion is a tool that shows how users go through your scenario step by step. You select a sequence of steps in a flow (for example: Welcome → Qualify → Offer → FD), and Chatterfy shows: how
Billing — bot expenses
The Billing tab in the shows how much it costs to run a specific bot. All expenses are collected here: using the bot itself, AI model calls, AI Reply, AI Routing, and AI Recognition. This section help
Analytics — detailed table
Раздел Tracker → Analytics — детальная таблица всех метрик Tracker с возможностью фильтровать, группировать и экспортировать в CSV. В отличие от , which shows an overview and charts, Analytics is a wo
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)
Send event — manual event triggering
The Send event button in → the Events tab allows for manual event sending for a specific lead. Unlike the automatic step that triggers within a funnel, here the operator decides to send an event to a
AI Reply — smart replies via AI
The AI Reply step is the main step for communicating via AI. In this step, the bot generates a response using a neural network, taking into account the lead’s message, the conversation context, flow-l
Push Messages — Re-engaging Silent Users
Push messages are delayed messages that are sent if a lead does not respond at the current step. This is a nurturing tool: the first reminder after 10 minutes, the second after an hour, the third the
Show Chat Events — displaying service events
The Show Chat Events block in → the Chat data tab — a toggle for displaying system events inside the conversation. When enabled, technical entries appear in the chat feed alongside regular messages: s

Was this article helpful?

BackBilling — bot expenses

On this page

  • When to open this section
  • 10 metrics
  • Charts
  • Period
  • How it differs from Tracker → Analytics
  • What each metric reveals
  • Low Dia → Reg (< 20%)
  • Low Reg → FD (< 10%)
  • Low FD → RD (< 1.2)
  • Use cases
  • Campaign evaluation after 30 days
  • Failure diagnosis
  • A/B test for retention via Push Messages
  • What to keep in mind
  • FAQ
  • Related