Skip to content
ChatterfyHelp Center
HomeGeneralCRMAI ManagerTrackerPlatformsFAQUpdate log
Main
Bot Settings
Automation & AI
CRM defaults
Flow Settings
AI Settings
Steps
Communication
Changes
Terms
Tracking
Tracking — sending events externally
Send event — sending an event to Tracker
Webhook — Sending Data Out
Additional
Messenger
Client card
Chat data
Events
Users
Mailings
Analytics
  1. CRM
  2. Tracking
  3. Send event — sending an event to Tracker

Send event — sending an event to Tracker

The Send event button in → tab — manual event sending for a specific lead. Unlike the automatic step in a flow ( → Send event), here the agent decides to send an event to a specific user manually and

Updated August 30, 20264 min
The Send event button in Customer Card→ tab Events — Lead Event Feed— manual event sending for a specific lead.
Unlike the automatic step in a flow ( Tracking — sending events externally→ Send event), here the agent decides to send an event to a specific user manually and at the current moment.
System events Registration, Deposit (sale), Redeposit (resale) are available, as well as custom events with their own names.
  1. Registration
  1. Deposit (sale)
  1. Redeposit (resale)
From the system's perspective, manual sending works the same way as:
  1. postback from a partner
  1. automatic Send event step
Event:
  1. enters Tracker — Overview
  1. is linked to a campaign via clickid
  1. is included in analytics and statistics


When to use

  1. The lead confirmed payment manually in the chat
  1. Support verified a deposit screenshot and wants to record the FD
  1. Need to trigger an event manually
Send event step
Send event step in the tree



Manual vs Auto Send event vs Postback

These are three different ways to send the same event.
Method
Where to find
When it triggers
Who launches it
Manual Send event
Client card → Events
Via button
Operator
Send event step
Flow
When a lead passes a step
Flow Settings
Postback
Partner URL
After an action in the partner program
Partner system
All three methods provide the same result — the event is logged in Tracker and included in analytics. Manual Send event is used when an event needs to be recorded manually.


Event types

Event
What it means
When to send manually
Registration
Registration in the partner program
Postback did not arrive, testing
Deposit (sale)
First deposit
Payment confirmation, testing
Redeposit (resale)
Repeat deposit
Repeat payment confirmation
Use a custom event for actions not covered by system types. Specify a short, permanent name, such as kyc_completed or application_approved. The spelling must match in the manual form, Flow Settings, and S2S settings.
Read more about event types in the Chatterfy glossary (section "Affiliate Events"): Subscribe / Registration / Deposit / Redeposit.


How to send an event

  1. 1

    1. Open the chat in Messenger

    In Messengeropen the required dialogue.
    Go to the tab Events — Lead Event Feed.
  2. 2

    2. Click Send event

    The event submission form will open.
  3. 3

    3. Select the event type

    Registration
    Deposit (sale)
    Redeposit (resale)
  4. 4

    4. Fill in the parameters

    For Deposit / Redeposit, you must specify the amount and currency in ISO format.
    Examples: USD. EUR. BRL.
    No additional fields are required for Registration.
  5. 5

    5. Click Save

    After clicking Save, the event is sent to the Tracker, appears in the lead's Events, and is included in analytics.
    Save is irreversible. Once sent, the event immediately affects campaign statistics and Tracker analytics. There is no undo. If an event is sent to the wrong lead, with the wrong type, or with an incorrect amount, adjustments are only possible through Chatterfy support.


Campaign Attribution

The event is automatically attributed to the campaign through which the lead arrived.

If the lead has Tracker Data

Example: Campaign → FB Q1 Forex India. In this case, the event will be attributed specifically to this campaign.

If the lead is organic

If the user arrived without a clickid, directly via Telegram, or through a standard link, the event will be attributed to the organic Tracker campaign.
The logic is identical to the automatic Send event step in the flow ( Tracking — sending events externally).


Usage examples

Postback did not arrive

The lead registered in the partner network, but Registration is missing from Events. Operator: Events → Send event. Registration. Save. The event appears for the lead and in Tracker analytics. Following this, tags, Condition branches, Change status, and other flow actions can trigger automatically.

Confirming payment in chat

The lead sent a screenshot of the receipt and confirmed payment in the chat. Partner postbacks arrive only after manual moderation and may be delayed. Manager: Send event. Deposit (sale). specify the amount. Save. The lead immediately enters the FD-segment, sales analytics, and branches after the FD.

Testing flows

The team checks the scenario after Registration. The test account completes the first steps. To avoid real registration: Send event. Registration. Save. The flow continues execution as if after a real postback.


Important considerations

Manual events affect analytics just like real postback events. Sending test or "fake" FDs will skew campaign and conversion statistics. Use Manual Send event only when the event actually occurred or in a test environment.
Duplicate events are possible. If you send an event manually and a postback from the partner arrives later, Tracker will count both events separately. There is no automatic deduplication. Before manual submission: check the Events tab, ensure the event is not already present. If the postback might be delayed, wait 30–60 minutes. If the postback is consistently delayed, it is better to coordinate the process with the partner.


Frequently asked questions

Yes. Choose a custom event and specify its permanent name. It can be used in Flow Settings and S2S-postbacks.

Manual Send event: triggered manually by an operator. Used for exceptions and adjustments.
Send event step: works automatically. Triggered by flow logic.
Both methods create the same event in Tracker.

No. There is no Undo.
If an event was sent by mistake, please contact Chatterfy support.

Yes. FD / Deposit can be sent even without Registration.

Into the organic Tracker campaign.
The event will be included in the general statistics, but not within the advertising campaign.

At the moment, manual event submission is not displayed in Logs — company activity log.


Related

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)
Flow Settings
The Flow Settings section is the heart of Chatterfy . This is where the bot’s communication logic with the lead comes together: which messages are sent, in what order, which conditions are checked, wh
Tracking — sending events externally
The Tracking category is steps that send data outward . They do not communicate with the lead or change the lead’s data inside Chatterfy — they send events and parameters to external systems. Tracking
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 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
Campaigns — advertising campaigns
It is the Campaign that connects Domain, Landing, Source, Telegram, tracker parameters, analytics, and events within the CRM. Once launched, the Campaign Tracker begins to: create tracking links recor

Was this article helpful?

BackTracking — sending events externallyNextWebhook — Sending Data Out

On this page

  • When to use
  • Manual vs Auto Send event vs Postback
  • Event types
  • How to send an event
  • Campaign Attribution
  • If the lead has Tracker Data
  • If the lead is organic
  • Usage examples
  • Postback did not arrive
  • Confirming payment in chat
  • Testing flows
  • Important considerations
  • Frequently asked questions
  • Related