◾Automation Rules
This document describes the purpose of the Automation Rules, the two different types - Realtime Automation Rules and Scheduled Automation Rules, and their specifics.
Last updated
This document describes the purpose of the Automation Rules, the two different types - Realtime Automation Rules and Scheduled Automation Rules, and their specifics.
Last updated
Automation rules are predefined conditions or criteria that are set to trigger specific actions or workflows automatically. With Smartico operators can set Real-time and Scheduled Automation rules. The main difference between the two types is that real-time rules require a trigger event to start the execution, and scheduled ones will start automatically when the execution schedule is set.
With the automation rules, operators can define a specific segment of players and perform automatically various processes. For example, to add/deduct/reset points, give bonuses, give mini-games, change levels, give missions, start/stop campaigns, mark/unmark users, and many more.
Use Automation Rules when you need to cover simple "if-then" cases or make an action on accumulation, like "Give 1 point for every 100 bets". They are extremely high-performing and can execute thousands of simple actions in a matter of seconds.
Real-time Automation Rules are triggered by events such as Deposits, Bet Placement, Level Change, Complete KYC flow, Mission unlocked, Mission completed, etc. Here are some definitions of the available options for Real-time Automation Rules:
Segment - targeted users. For example:
All VIP Bronze customers
All customers with a deposit count > 1
Customers from Canada
etc
Trigger event - The event that will start the rule execution. The entry trigger can be any event defined in the system:
Deposit approved
User login
Sport bet
Casino bet
Mission completed
Changed level
etc
Estimate Audience size - when clicked it gives the exact number of users included in the segment. The estimation of the segment size is based on the state of users on the current date.
Accumulation - for example: give 1 point when the end-user is wagering 10 EUR / 8 GBP / 12 USD, depending on the user's wallet currency. The 1 point will be issued every time the user reaches a total wagering amount. Read more at: https://help.smartico.ai/welcome/more/release-notes/january-2022#automation-rules-based-on-the-value-accumulation
It is important to note that if the user makes a 10.5 EUR deposit in one transaction, he will get 10 points, and the remaining 0.5 EUR will be remembered for future accumulation. The total number of "executions" in one transaction is limited by 1000, which means that if the user makes a 2000 EUR deposit in one transaction, he will get only 1000 points. This is done to prevent human mistakes that will lead to many activities being executed.
Once-in-a-lifetime option - when enabled the rule will be executed only once for a specific user
Activity Period - when the automation rule will be executed. You can restrict the rule to run only during a specific date range and include only specific days of the week.
Starting from a specific time but without an end date
Finishing on a specific date, but without a start date, so it will be active immediately
Setting a specific date period
Leaving both fields empty, so it will run until explicitly stopped
Only on specific days of the week
Activity type - what will be the action towards the player - give points, give bonus, give mission, start a campaign, etc.
Qualification trigger for Automation rules - available only for Realtime Automation rules. This feature allows you to set a trigger to determine if the automation rule should be executed. If this condition isn't met, even if the trigger event has happened, the specified activity in the rule won't be executed for the players. For example, suppose the qualification trigger is 'Deposit' and the rule requires placing 100 bets for a bonus. In that case, players who meet the bet condition without making a deposit won't receive the bonus.
In addition, the Qualification trigger has 2 more options:
Qualification Period - counting the period till the qualification condition is valid. When set, the automation rule will count users' actions only during the specified period. If users don't meet the automation rule requirements within this period, the activity won't be executed, but they can requalify by meeting the qualification condition again. For example, you can set a qualification trigger to be ‘Deposit’ and a rule requirement to make 100 bets in 24 hours after qualification to get a Bonus. If the users don't make 100 bets, they will not get the bonus but can be qualified again if they deposit again.
Rule iteration - Number of times the rule can be completed after qualification. Defining how many times the automation rule can be executed before players must requalify to receive the specified activity. For example, if the qualification condition is to Deposit 100EU, the automation rule requires placing 5 bets, and the Rule iteration is set to 3 - the players can meet the betting requirement only 3 times afterward, they'll need to deposit 100 Euro again to get the bonus.
Qualification event is not counted as part of the progress in the Automation Rule, meaning that when the qualification condition is met, the players are qualified to progress.
If the automation rule isn't limited to a ‘once-in-a-lifetime’, the ‘Rule iteration’ is not set, and the qualifying condition is met at least once, players will receive the bonus every time the automation rule requirements are fulfilled.
The Qualification option is available in the BO, within the Realtime Automation Rules section, and by default is disabled. Once enabled, 2 new columns will appear in the ‘Execution History’ tab.
Qualification date - when the user has fulfilled the qualification condition
Qualification validity - showing the period until the qualification is valid if the qualification time limit is set.
Scheduled Automation Rules are triggered on a defined schedule such as daily, days of the week, days of the month, one time on a specific day, etc. You can create a rule targeting a specific segment of users on a defined schedule. Read more at: https://help.smartico.ai/welcome/more/release-notes/august-2023#scheduled-automation-rules
Here are some definitions of the available options for Scheduled Automation Rules:
Segment - targeted users. For example:
All VIP Bronze customers
All customers with a deposit count > 1
Customers from Canada
etc
Extra Conditions for the segment of users - for example, to add more conditions to the segment like users who have X remaining spins in Y Mini-games or users that are registered in a specific tournament, etc.
Execution Schedule - when the automation rule will be executed. For example - daily, specific days of the week, custom schedule, only one time, etc.
Starting from a specific time but without an end date
Finishing on a specific date, but without a start date, so it will be active immediately
Setting a specific date period
Leaving both fields empty, so it will run until explicitly stopped
Only on specific days of the week
One time - send now and mark as executed
Only on specific days of the month
Execution Speed - Configuring the automation’s rule sending rate - for how many users the rule will be executed per minute.
