The action “Credit cashback” allows scenarios to automatically credit a specified amount of cashback to the user's balance when the scenario is triggered. This is a convenient way to reward users without any manual actions.

For example, you can set up a scenario that automatically adds 50 cashback to a client’s balance after their first order, registration in the app, or on their birthday — fully automatically.

Scenario Setup:

1. In the Control Panel, select the Marketing section
2. Go to the Scenarios tab = Create

Filling out the "General" tab:

• Name. Descriptive name of the scenario (for example, "Credit points after order cancellation")

• Status. Set the active status.

Active — the scenario will execute when the trigger is activated.

Inactive — the scenario will not start for new triggers, but all tasks that have already been started will be executed.

• Trigger. Select from the dropdown list. The event that activates the scenario.

• Limit scenario. Optionally, you can set restrictions for the trigger.

This allows you to narrow which orders should activate the scenario. When "Limit trigger" is enabled, you can configure the following filters:

• Limit by order source type

Limits the scenario to orders from certain platforms. For example, only orders from the mobile app or only from the website.

• Limit by delivery type

Limits the scenario to certain types of delivery (e.g., delivery, pickup, in-hall).

• Minimum / Maximum order price

Limits the scenario to orders within a certain price range.

• Minimum order price — the scenario will only trigger for orders equal to or above this amount.

• Maximum order price — the scenario will only trigger for orders equal to or below this amount.

| Example: You want to credit cashback points only for orders over 50$ made through the mobile app. Enable the trigger restriction with order source = App and minimum price = 50.

• Delay period and Delay value. Time to wait after the trigger before executing actions, i.e., how long to wait before performing the configured scenario action.

• Execute only once per order and Execute only once per user. These settings prevent duplicate scenario execution:

| Parameter | Description |

| Execute only once per order | If enabled, the scenario will create only one task for a single order. Even if the trigger fires multiple times for the same order, only the first task will be created. |

| Execute only once per user | If enabled, the scenario will create only one task for a single user. After creating a task for the user, no new tasks for this scenario will be created for them. |

| Example: If "Once per user" is enabled for the scenario, the client will only receive credited points once — even if they make multiple orders.

• Cancellation conditions define events that will cancel a pending scenario task before it executes. This is useful when scheduled actions are no longer relevant.

Available cancellation conditions:

| Condition | Level | Description |

| Creation of a new order | User level | Cancels the task if the same user creates a new order (any order, not only related to the trigger) |

| Cancellation of the current order | Order level | Cancels the task if the trigger order is canceled |

| Completion of the current order | Order level | Cancels the task if the trigger order is completed |

| Leaving a review on the current order | Order level | Cancels the task if a review is left for the trigger order |

Important notes:

● Cancellation conditions only apply to tasks with the status "Waiting for execution" (not yet executed).

● You can select multiple cancellation conditions — if any of them triggers, the task will be canceled.

● Order-level conditions check the specific order that triggered the scenario.

● User-level conditions check any user activity across all orders.

• Success conditions.

Success conditions track whether the scenario achieved the desired goal after executing actions. This is optional — success conditions are only needed if you want to measure the scenario’s effectiveness.

Enabling success conditions

Toggle "Has success conditions" to enable this feature. Then configure:

Available success conditions

● Success condition: "Creation of a new order"

● Waiting time: 7 days

● If the client places a new order within 7 days after cashback credit → task result "Successfully completed"

● If 7 days pass without an order → task result "Conditions not met"

This allows viewing the scenario success rate on the tasks page.

Filling out the "Actions" tab:

1. In the scenario actions form, enable the switch «Credit cashback». After enabling, an additional field will appear below.
2. In the field "Cashback credit amount", enter the amount of cashback to be credited to the user's balance. The value must be a positive number.

Examples:

3. Click "Save" to apply the settings. Cashback crediting will be active the next time this scenario is triggered.

The action “Credit cashback” works independently of other scenario actions. It can be enabled together with:

• “Send message” — to notify the user about the credited cashback via SMS or Push
• “Generate promo code” — to also provide the user with a promo code in the same scenario

For example, you can set up a scenario that credits cashback and sends a Push notification to inform the user.

Hello, {{userName}}! Bonus cashback has been credited. Check your balance!

Example of "Actions" tab settings

How the scenario will work:

When the scenario is triggered for a user:

1. The system checks that the user exists and the cashback amount is greater than zero.
2. The specified cashback amount is credited to the user's cashback balance.
3. The transaction is recorded with the note “Cashback credited by scenario” for tracking.
4. Cashback is added asynchronously, so the scenario execution continues immediately without delays.

| Important! Cashback crediting is processed as a manual transaction. It appears in the user's cashback transaction history with type “Manual” and note “Cashback credited by scenario”.

What happens if the cashback amount is set to 0?

Cashback will not be credited. The system skips this action if the amount is zero or not specified.

What happens if the user does not exist?

Cashback crediting will be skipped. No error will be shown, and other scenario actions will continue to work normally.

Can I specify a fractional amount (e.g., 10.50)?

Yes. The amount field accepts decimal values. The system correctly processes amounts like 10.50 or 25.75.

Where can I see credited cashback?

Credited cashback appears in the user's cashback transaction history. Look for transactions with type “Manual” and note “Cashback credited by scenario”.

Can it be combined with other actions in one scenario?

Yes. “Credit cashback” works independently of other actions. It can be enabled together with “Send message” and “Generate promo code” in one scenario.

Is cashback credited immediately?

Cashback is credited asynchronously (via background task). In practice, it appears on the user's balance within a few seconds after the scenario triggers.

Does this work for all scenario triggers (order, registration, birthday, etc.)?

Yes. The cashback action can be used with any type of scenario trigger. It simply adds cashback to the user associated with the trigger event.

Link to the article: here.

Updated on: 29/03/2026