Skip to content
ChatterfyHelp Center
HomeGeneralCRMAI ManagerTrackerPlatformsFAQUpdate log
Tracker
Dashboards
Campaigns
S2S Postbacks — Sending Events from a Campaign
Campaigns — advertising campaigns
How to create a campaign
Information — Basic Campaign Identification
General — user journey
Auto Actions — auto actions based on postbacks
Parameters — link parameters
Filters — traffic filters
Test — checking a campaign before launch
Invite + DM — Hybrid Scenario
Sources
Domains
Landings
Analytics
Cohorts
Leads
Integrations
  1. Tracker
  2. Campaigns
  3. Auto Actions — auto actions based on postbacks

Auto Actions — auto actions based on postbacks

The Auto Actions tab lets you automatically change a lead’s state in CRM when an affiliate network event occurs. Without operator intervention: a postback arrives — the lead switches to the required F

Updated August 30, 20263 min
The Auto Actions tab lets you automatically change a lead’s state in CRM when an affiliate network event occurs. Without operator intervention: a postback arrives — the lead switches to the required Flow or gets a new status.
When to use Auto Actions
You want to move a lead to a special “post-deposit” Flow with repeat deposit offers. After registration (but before the deposit), switch them to a warm-up Flow so AI or an operator can bring them to payment. When a withdraw event arrives, tag the lead as “withdrew funds, be careful” and set Status to Manual for an operator. After a resale event (repeat deposit), put them into the “already ours, run repeat sales” Flow. Any situation where “event → action” can be automated.

How it works

When the affiliate network sends a postback with an event (registration, sale, resale, withdraw, any custom event), Tracker:
  • Finds the lead by clickid.
  • Logs the event in the lead card (Events section).
  • Checks the Auto Actions rules for the campaign the lead came through.
  • If there is a rule matching the event, applies it: switches Flow / Step and/or changes Status.
Without Auto Actions, the event is simply written to the log, and the operator decides what to do. Auto Actions is an event “handler” that works without operator involvement.



Rule setup steps

  1. 1

    Open the campaign

    Tracker → Campaigns → select a campaign → Edit.
    
  2. 2

    Go to the Auto Actions tab

    You will see a list of existing rules and the Add action button.
    
    Add action
    Add action button
    
  3. 3

    Select an event (Event)

    For example, sale (first deposit) or registration. The list depends on the events configured in Integrations — Partner Programs.
    
  4. 4

    Fill in the action

    Specify Flow, Step, and Status. All three are optional: you can set only Status, or only Flow + Step, or everything at once.
    Flow / Step / Status fields
    Flow / Step / Status fields
    
  5. 5

    Save

    Save button. The rule applies to new events. Existing leads are not changed — Auto Actions does not “catch up” retroactively.
    
    Save button
    Save button
    


Rule parameters

Field
What it defines
Type / example
Event
Event type from the postback. The rule is triggered when this event comes from the affiliate program.
sale/registration
Flow
Which Flow to move the lead to. Optional — if not specified, the Flow remains unchanged.
Hot Lead Flow
Step
The specific Step within the Flow where the lead will go. Optional, but usually specified.
After Deposit
Status
Which dialog status to set. Auto /Manual/Stopped/Finished. Optional.
Manual


Usage examples



After registration — warm-up — media buying

The Buyer wants a lead who registered in the affiliate program but did not make a deposit to receive a series of push notifications with reminders. Rule: Event =registration, Flow =Warm-Up, Step =Day 1 Reminder. Inside the Warm-Up Flow — Статьяwith a schedule for 1, 3, and 7 days.


After the first deposit — repeat sales — media buying

The lead made an FD — it is time to offer a repeat deposit and more advanced affiliate products. Rule: Event =sale, Flow =Hot Lead, Status =Manual(so an operator can step in). Optionally, Auto Action adds the tag depositor.


After withdrawal — operator flag — arbitration

Withdraw — the lead has withdrawn money. Rule: Event =withdraw, Flow =Recovery, Status =Manual — the operator steps in and tries to retain the lead, or at least find out the reason for the withdrawal for analytics.


Universal scenario — sales

The sales team uses the custom event purchase from the payment system. Rule: Event =purchase, Flow =Customer Onboarding — after payment, the customer automatically moves to the onboarding Flow; the bot explains the product, schedule, and support contacts.
What to keep in mind
Auto Action is triggered once per event — if the lead made a sale, the rule was triggered. A repeated sale without resale will not start it. Without a valid clickidTracker, it will not be able to find the lead and the rule will not be applied — check in Logs — журналы событий. Auto. Auto Actions work only for events received via postbacks Integrations — Partner Programs— Subscribe / Click / Contact events come from Chatterfy itself and are not configured here. You can create several rules for one event — all of them will be applied sequentially (but this is usually unnecessary; one rule is better).


Frequently asked questions

Check: postbacks are actually coming in (see Logs — журналы событий), the postback Status = OK (the lead binding was found), and the correct Event name is specified in the rule (for example, the affiliate network sends “sale” but the rule says “sales” — mismatch). Also check that the DM bot / Bot is active — if the bot is disabled, moving to a Flow will not work.

If you want to start new messages / a new scenario after an event — use Flow + Step. If you just need to “flag for an operator” — use only Status = Manual (this will remove the lead from automatic processing and add them to the operator queue). You can combine them: Flow + Status (a new Flow with the Manual flag).

Directly in Auto Action — no; there are no amount-based conditions. Alternative: inside the specified Flow, use Статья Terms steps (conditions based on Статья), which check the deposit amount (received in tracker.cost) and branch the logic.

Yes, each campaign has its own set of rules. A lead is linked to a campaign via clickid at the moment of the click — the rules are applied from the campaign they came through. If the lead came through Campaign A and made a deposit, Campaign A’s rules are applied, not B’s.

Yes, there is a delete button next to the rule. After deletion, new events of the same type will not trigger this action. Existing leads to whom the rule was applied remain in their current Flow / Step.


Related

Integrations — Partner Programs
The Tracker → Integrations section is for connecting affiliate programs to Tracker . When a lead registers or makes a deposit with the affiliate program, it sends a postback (HTTP request) with an eve
How event forwarding works
This article is a mental model of how Tracker links affiliate program events to specific leads. After reading it, you will understand why a postback must contain clickid , what happens if the macro is
Parameters — link parameters
Parameters is the campaign tab where link markup is configured: which parameters will be added to the campaign URL and which data will be saved with the lead after they click the link. Campaign tracki
Logs — журналы событий
Откройте Tracker → Logs. В верхней части страницы доступны четыре журнала: отправка постбэков, события источников, S2S-запросы и история изменений объектов Tracker. Для поиска одной цепочки используйт

Was this article helpful?

BackGeneral — маршрут пользователяNextParameters — link parameters

On this page

  • How it works
  • Rule setup steps
  • Rule parameters
  • Usage examples
  • After registration — warm-up — media buying
  • After the first deposit — repeat sales — media buying
  • After withdrawal — operator flag — arbitration
  • Universal scenario — sales
  • Frequently asked questions
  • Related