The trigger App Registration allows you to create automated marketing scenarios that are activated when a new user registers via the mobile application (iOS or Android).

For example, you can automatically send a welcome push notification, an SMS with a promo code, or accrue cashback to a user who has just installed the app and registered.

This trigger belongs to the group of "User" triggers, unlike triggers related to orders ("Order Created" or "Order Completed"). It does not require creating an order — it is triggered immediately after user registration.

How to configure the scenario:

1. In the Control Panel, select the Marketing section
2. Go to the Scenarios tab = Create
3. Fill in the Name field - the name of the scenario.
4. In the Status field, set the Status to “Active” if you want the scenario to start working immediately, or “Inactive” to configure it first and activate it later.
5. In the Trigger dropdown list, select App Registration. This tells the system to run this scenario every time a user registers via the mobile application.
6. (OPTIONAL) Configure platform restrictions.

If you want the scenario to apply only to users who registered from a specific platform, enable the Limit trigger switch.

Two checkboxes will appear:

• iOS - the scenario is triggered only for users who registered via the app on iPhone/iPad
• Android - the scenario is triggered only for users who registered via the app on Android

||| If both checkboxes are selected (or the "Limit trigger" switch is disabled), the scenario will be triggered for all registrations via the app regardless of the platform.

7. (OPTIONAL) Set a Delay.

You can configure a delay before executing the scenario actions. For example, send a welcome message 5 minutes after registration instead of immediately. Available delay units: seconds, minutes, hours, days, weeks, months.

8. (OPTIONAL) Configure One time per user.

Enable Execute only once per user if you want the scenario to be triggered only on the first user registration. This prevents the same user from receiving the scenario actions again (for example, if they delete and reinstall the app).

9. (OPTIONAL) Configure One time per app.

Enable Execute only once per app if you want the scenario to be triggered only once for each device/app installation. This is useful when you need to limit execution to one time per device, even if the same user registers again.

10. Cancellation Policy and Conditions for Success are configured optionally; for this trigger, they do not need to be configured, they are not mandatory.
11. Save the scenario settings and go to the "Actions" tab to configure what happens when the scenario is triggered.

Configuring "Actions"

When the App Registration trigger is triggered, you can configure the following actions:

1. Generate promo code - generates a unique promo code for the user based on the selected campaign. The code can be included in the message text.
2. Send message:

• Send Push notification - sends a push notification to the user's device. You can set the title, message text, and the app screen for navigation.
• Send SMS - Sends an SMS message to the user's phone number.

When writing the text of a push notification or SMS, you can use placeholders that are automatically replaced with user data:

{ userName } = user name

{ userPhone } = user phone number

{ promoCode } = generated promo code (available only when the "Generate promo code" action is enabled)

| Please note: Placeholders related to orders (such as { orderNumber } , { companyName }) will be empty for "App Registration" scenarios, since the order is not associated with this trigger, so it is not relevant to add them to the message text.

3. Accrue cashback - adds a cashback amount to the user's balance.

Scenario examples:

Example №1. Welcome Push for new iOS users

Goal: Send a welcome push notification to users who have just registered via the iOS app.

Trigger: App Registration

Platform restriction: iOS only

Delay: none (send immediately)

One time per user: Yes

Action: Send Push — Title: "Welcome!", Message: "Hello, { userName }, thank you for registering! Enjoy your first order."

Example №2. Promo code for all new app users

Goal: Provide each new app user with a unique promo code for a 10% discount.

Trigger: App Registration

Platform restriction: none (iOS and Android)

Delay: 1 minute

One time per user: Yes

Action 1: Generate promo code — Campaign: "10% Discount", Valid: 7 days

Action 2: Send SMS — "Welcome, { userName }! Use code { promoCode } to get a 10% discount on your first order."

Example №3. Cashback for Android users

Goal: Accrue 50 UAH cashback to all new Android app users.

Trigger: App Registration

Platform restriction: Android only

Delay: none

One time per user: Yes

Action: Accrue cashback — Amount: 15

Will this trigger work if the user registered via the website?

No. The "App Registration" trigger works only when a user registers via the mobile application (iOS or Android). Registrations via the website are not covered by this trigger.

What happens if both iOS and Android checkboxes are unchecked?

If the "Limit trigger" switch is enabled but no platform is selected, the scenario will not be triggered for any registration. Make sure at least one platform is selected, or disable the "Limit trigger" switch to cover all platforms.

Can placeholders related to orders be used?

Order placeholders such as { orderNumber } or { companyName } will be empty for "App Registration" scenarios, since the order is not involved. Use { userName } and { userPhone }.

Does "One time per user" prevent triggering on app reinstallation?

Yes. If "One time per user" is enabled, the scenario will be triggered only once for each unique user, regardless of the number of reinstalls and registrations.

Can this trigger be combined with actions related to orders?

The actions themselves (push, SMS, cashback, promo code) work the same. However, cancellation and success conditions related to orders (for example, "cancel if order is canceled") do not apply to this trigger.

What is the difference between "One time per app" and "One time per user"?

"One time per user" ensures one execution per user account. "One time per app" ensures one execution per device/app installation. One user can trigger the scenario on two different devices if only "One time per app" is set (but not "One time per user").

Link to this article: here

Updated on: 29/03/2026