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
The Send event button in Customer Card→ the Events tab allows for manual event sending for a specific lead. Unlike the automatic Flow Settings step that triggers within a funnel, here the operator decides to send an event to a specific lead right now.
System events such as Registration, Deposit (sale), and Redeposit (resale) are available, as well as custom events with your own naming.
From the system's perspective, manual sending is the same as a postback from a partner or an automatic step from a flow: the event enters the
Tracker (TRACKER → How Tracker works), links to the campaign via clickid, and is recorded in analytics.When to use
Postback did not arrive — partner did not configure it, wrong URL, limits — send manually.
Testing flows — need to simulate that a lead has completed registration.
Confirming actions from a source outside Chatterfy — lead sent a receipt screenshot in chat, confirmed payment in correspondence, or information came from another team.
Support received a deposit screenshot and performed a manual check — need to record the First Deposit (FD).
Manual vs Auto Send event vs Postback
These are three different trigger points for the same event type:
Method | Where | When it triggers | Who triggers it |
Manual Send event | Lead card → Events | Upon operator click | Operator |
Send event step | Step in a flow | When a lead reaches the step | Flow logic / AI / Condition |
Postback | External partner URL | When a lead has completed an action in an affiliate program | Affiliate program |
All three points have the same effect — the event is sent to
Tracker and accounted for in analytics. The only difference is who triggers the sending. Manual is for cases where automation did not work or if you need to simulate an event.Event types
Event | What it means | When to send manually |
Registration | Registration in an affiliate program | Postback was not received, flow testing |
Deposit (sale) | Lead's first deposit | Confirmation from a source outside Chatterfy, testing |
Redeposit (resale) | Repeated deposit | Confirmation from a source outside Chatterfy, testing |
Use a custom event for an action that is not among the system types. Specify a short, consistent name, such as kyc_completed or application_approved. Its spelling must be identical in the manual form, Flow Settings, and S2S settings.
A full breakdown of each type can be found in the Glossary (GENERAL → Glossary) (section "Affiliate events").
Sending steps
1. Open the chat in Messenger
Go to the Events tab in the client card.2. Click Send event
The event selection form will open.3. Select the event type
Registration / Deposit (sale) / Redeposit (resale) or a custom event.4. Fill in the parameters
For Deposit / Redeposit, you must specify the amount and currency in ISO format (e.g., USD, EUR).For Registration, no additional parameters are required.5. Click Save
The event is sent toTrackerand appears in the Events feed for this lead.Save is irreversible.After clicking Save, the event is recorded inTrackerand the client card—it will affect campaign statistics. A sent event cannot be undone. If you made a mistake (sent the wrong type or to the wrong lead), contactChatterfysupport with a link to the chat; manual correction is only possible on their side.
Linking to a campaign
The event is automatically linked to the campaign through which the lead arrived (via clickid):
If the lead has a filled Tracker Data — traffic source data— for example, campaign FB Q1— the event will be counted in this campaign.
If the lead is organic (without a clickid) — the event will be counted in the
Tracker "organic" campaign.Usage examples
Arbitrage — postback not received
A lead registered in the affiliate network, and the operator is aware of it (the partner sent a screenshot to support). There is no Registration in the lead's Events — the postback was lost.
Operator → Send event → Registration → Save.
The event appears in the lead's Events and in
Tracker analytics.The registered tag will be automatically applied via Condition — conditional branchingво флоу, если такая логика настроена.in the flow, if such logic is configured.
Sales — confirming payment in a conversation
A sales manager is chatting with a lead. The lead sends a screenshot of a receipt and confirms: "Paid for the course via bank transfer." The partner (the course platform) only processes the postback after manual moderation — this can take several hours.
The manager does not want to wait:
Send event→Deposit (sale) with an amount →Save.
The lead immediately enters the FD segment in analytics, and you can start re-engagement or make a repeat offer.
Testing the scenario
Команда настраивает новый флоу с веткой после Registration. Тестовый лид (свой
Telegram-аккаунт) прошёл первые шаги в чате.To check what happens after Registration:
Send event→Registration manually.
The flow is triggered on the branch after Registration — you can check the logic without a real registration in the partner program.
Important considerations
Affects analytics.
Ручная отправка события считается в общей статистике
Trackerточно так же, как постбек или auto-шаг. Если злоупотреблять (отправлять «фейковые» события для красоты графиков), искажается реальная конверсия. Используйте только когда событие реально произошло, но не дошло автоматически.Duplicate events with delayed postbacks.
Если постбек партнёра придёт после ручной отправки — событие задвоится.
Trackerне дедуплицирует автоматически. Перед ручной отправкой:Check Events — ensure the event has not already been logged.
If you are expecting a postback, wait at least 30–60 minutes (depending on the partner) before sending it manually.
If postbacks are systematically delayed, discuss this with your partner or switch to manual sending as a standard process.
FAQ
Related
Was this article helpful?