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
Custom Events
Events — Lead Event Feed
Send event — manual event triggering
Users
Mailings
Analytics
  1. CRM
  2. Events
  3. Events — Lead Event Feed

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)

Updated August 29, 20265 min
The Events tab in Customer Card— 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) is a separate event in this feed. It helps you see the full behavior history at a glance and understand which funnel stage the lead is currently in.
Events come from two sources:
From Chatterfy itself — Page View / Click / Subscribe / Contact (when the lead interacts with your landing pages and bot).
From the affiliate program via postback — Registration / FD / RD (when the lead performs actions in the affiliate program).
The category parallel to this tab is Tracking — sending events externally(flow steps that send events automatically when the step is reached). This tab shows what ultimately came in — regardless of whether it was sent from a flow step, from an affiliate postback, or manually via Send event.


When to open this tab

The lead registered — check whether the postback arrived.
You want to understand the path of a specific lead through the funnel.
The postback did not arrive and you need to send the event manually — use the Send event button.
Support asks “why didn’t this lead receive the reward?” — Events will show which events occurred and which did not.
Audit a specific campaign’s conversion — open 5 random leads from it and compare the events.
Confirm an off-channel event (the lead made a deposit by phone; you need to mark it manually).



Which events are visible

The lead’s full journey from first touch to repeat deposits:
Page View — the lead opened the landing page.
Click — clicked the button to go to Telegram.
Subscribe — subscribed to the channel or started the bot.
Contact — sent the first message to the bot.
Registration — registered in the affiliate program (via postback).
FD — First Deposit, the first deposit.
RD — Re-Deposit, a repeat deposit.
Each event includes a time, source (postback / manual / automatic), and parameters (deposit amount, transaction ID). A full breakdown of each type is available in Glossaryand in Tracker — Overview. The feed is sorted chronologically: the latest events are at the top, the history is below.


Auto vs Manual events

The same event type can appear in the feed in three different ways. Understanding the difference is important for debugging the funnel:
—Auto from flow: a step Send event — sending an event to Trackerinside the scenario sends an event when the lead reaches the step. For example, after AI Reply “I’ve sent you the registration link” — the next step is Send event = Registration. This lets you count the conversion even before the postback arrives.
—Auto from postback: the affiliate network makes an HTTP request to your postback URL → Tracker — OverviewChatterfy receives it → the event appears in this lead’s card. This is the “true” event — actually confirmed by the partner.
—Manual: the operator clicks the Send event button themselves and sets the event. Used when a postback was lost, or the event happened off-channel (by phone / in email). See Send event — manual event triggering.


What’s inside

One subsection — manual event sending.
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
Send event — manual sending— a button for the operator to send an event manually, bypassing postback. Useful when the automatic postback has not arrived, when testing a scenario, or when confirming an event from an off-channel source (call, email).


Use cases by segment

—Media buying: the buyer opens the Events feed for each “hot” lead to make sure Reg → FD went through. If Reg is there, but FD is not — continue warming up. If FD arrived, but on the wrong affiliate network — check the clickid in Tracker Data.
—Sales: after a call with a lead, a rep sets Manual = Registration / FD to record the fact and let the marketing team know that this campaign is working.
—Support / e-commerce: for a customer complaint “my bonus wasn’t deducted” — opens Events, sees that the FD event did not arrive → escalates it to the tech team with the chat and time specified.


Where to start

Simply open the Events tab in the client card and review the feed:
If there is Subscribe + Contact + Registration + FD — everything is OK, the lead has passed through the funnel.
If only Subscribe + Contact — the lead did not register / the postback did not arrive.
If there is Registration, but no FD — the lead registered but has not paid.
If there is nothing — the lead is organic and events are not tracked.
If the event should have happened but is missing — Send event — manual event triggeringfor manual sending.


Related sections

The Events tab in the client card is a snapshot of data from “Tracker — Overview” Tracker — Overview— the same events as in Tracker analytics. The full path from advertising to RD is visible in Tracker Conversion — conversion from conversation to RDand Tracker — Overviewanalytics. The logic of how events are ingested (postback URL, event types) is described in Tracker — Overviewintegrations.
Internal “technical” events (Change Status / Change Step / Error) are not shown here, but in Show Chat Events — displaying service events.


Frequently asked questions

First, check whether the postback URL is configured in the partner account, whether the correct clickid is being passed, and whether there are any errors in Tracker logs. If events are not coming in and are not supposed to, use Send event — manual event triggering to send them manually.

The event row shows the source. Postback is usually a label such as “from postback” / the campaign name. Manual is “sent manually by Ivan”. The time and the amount parameter are visible in both cases.

Currently, not in the client card: the feed is shown in full. If you need a selection by event type (for example, “all leads with FD for the last month”), use User filtering — 11 parameters with the Events parameter.

No. Postback events are always separate, on the Events tab. The conversation message feed shows only real messages and (optionally) service events via Show Chat Events — displaying service events.

With no time limit, for the lifetime of the chat. They are deleted only via Actions — exporting and clearing a conversation → Clear chat (irreversible). In Tracker, they are stored separately and independently.

Any number. RD = Re-Deposit = repeat deposit: each deposit after the first creates a separate RD event. VIP leads can have dozens of them. All of them are visible in the feed; in Tracker, they are also counted separately.

This tab is one lead (the history of a specific person). Tracker Conversion — conversion from conversation to RD and Tracker — Overview → Analytics are aggregates (overall conversion across all leads, breakdowns by campaign). Here you diagnose a specific case; there you see the overall picture.


Articles in this section

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


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
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
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
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

Was this article helpful?

NextCustom Events

On this page

  • When to open this tab
  • Which events are visible
  • Auto vs Manual events
  • What’s inside
  • Use cases by segment
  • Where to start
  • Related sections
  • Frequently asked questions
  • Articles in this section
  • Related