◾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.
Overview
Automation rules are predefined conditions or criteria that 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 execution, whereas scheduled rules begin automatically when the execution schedule is set.
Using automation rules, operators can define a specific segment of players and automate 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.
Real-time Automation Rule
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 users' states 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. 1 point will be awarded each 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
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 automation 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 particular date, but without a start date, so that it will be active immediately
Setting a particular period of date
Leaving both fields empty, so it will run until explicitly stopped
Only on particular days of the week
Activity type - what will be the action towards the player - give points, give bonus, give a mission, start a campaign, etc.
Qualification trigger for Automation rules - available only for Realtime Automation rules. This feature lets you set a trigger to determine whether the automation rule should execute. 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 to earn 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 100 EUR, 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 EUR again to get the bonus.
The Qualification option is available in the BO, under the Realtime Automation Rules section, and is disabled by default. 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.
Control group
You can define a "control group percentage" in the rule editor. At the time of rule execution, the system will randomly determine (based on the set percentage) whether a user receives the activity or is withheld as part of the control group.
If a user is selected for the control group, they’ll still progress through the rule logic as usual, but the set activity (e.g., rewards, messages) will be skipped.
Important to note:
The control group is not "sticky": if the user was selected for the control group on the 1st execution of the rule, it doesn't mean he will be in the control group on the next execution.
For the rules with accumulation, belonging to the control group decided at the moment of getting to the required accumulation target. E.g., if the rule is set to trigger on a total wager of 100 EUR, the rule will count the wager for the user, and when the wager amount reaches 100 EUR, the system will decide whether to execute the rule or skip it based on the target group. Keeping in mind the "non-stickness" logic of the control group, the next session of the same user who collected 100 EUR wagering may give a different result, and the user will be again selected to match or not to match the control group
Restrict Active Hours
The Restrict Active Hours feature in Real-time Automation Rules allows you to define specific timeframes during which a rule will be executed. This setting can be used independently or combined with the Activity Period option for greater control over automation timing.
How It Works
If only Active Hours are set (without a weekday or date restriction), the rule will run daily during the specified hours.
When combined with Start and End date in Activity Period, the rule’s execution depends on both date/time conditions.
When combined with Weekdays in the Activity period, the rule will take into account the selected weekdays + the Active hours.
For example, you can set a rule to execute only on Saturday and Sunday from 10:00 AM until 18:00.
Behavior When Combined with Start & End Dates:
Start date is earlier than Active Hours start time
The rule starts when Active Hours begin on the Start date.
Start Date: 03. 03. 2025, 08:00 AM Active Hours: 09:00 AM – 6:00 PM Rule starts: 09:00 AM, 03.03.2025
Start date is later than Active Hours start time
The rule starts at the Activity Period's Start Date and Time.
Start Date: 03. 03. 2025, 10:00 AM Active Hours: 09:00 AM – 6:00 PM Rule starts: 10:00 AM, 03.03.2025
End date is earlier than Active Hours end time
The rule stops when the Activity Period’s End Date and Time is reached.
End Date: 03. 03. 2025, 06:00 PM Active Hours: 09:00 AM – 7:00 PM Rule stops: 06:00 PM, 03. 03. 2025
End date is later than Active Hours end time
The rule stops when Active Hours end on the End Date
End Date: 03. 03. 2025, 06:00 PM Active Hours: 09:00 AM – 4:00 PM Rule stops: 04:00 PM, 03. 03. 2025
Scheduled Automation Rule
Scheduled Automation Rules are triggered on a defined schedule, such as daily, on specific days of the week or month, or once on an exact day. You can create a rule targeting a particular 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 who 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 once, etc.
Starting from a specific time but without an end date
Finishing on a particular date, but without a start date so that it will be active immediately
Setting a specific period of dates
Leaving both fields empty, so it will run until explicitly stopped
Only on particular 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.
Manually Stop a Scheduled Automation Rule
The ‘Stop Rule’ option in Scheduled Automation Rules allows you to stop the rule's execution manually. This option is located under the ‘More’ button and is only available when the rule is about to execute (5 minutes before the set date) or is currently running. If the rule is inactive or active but not close to execution, the option will be greyed out, as you can manage the rule’s status.
When you manually stop a rule:
All current and future runs are halted
Pending users will no longer progress
The rule’s status changes to ‘Inactive’, but you can reactivate it anytime.
Limit the activities given by the Automation Rule.
You can control how many times an activity from an automation rule can be awarded to each user within a defined period. Once a user reaches the limit, no additional activities will be granted until the next period starts. This setting - “Max number of activities given per period” is available in the Activity Details modal for both real-time and scheduled automation rules. For example, if an automation rule gives a bonus, you can limit it to 3 per day per user, meaning each user can receive it only 3 times per day.
Note: If “Once in a lifetime” is enabled, the “Max number of activities given per period” option will not be available.
This option also applies to accumulation-based rules. For instance, if a rule awards 1 point for every 100 EUR bet and is limited to 1 execution per hour, and a user places a single 500 EUR bet, they will receive only 1 point. The rule logs one execution, does not grant multiple points, and does not carry over unused bet amounts. When the next period begins (hour/day), the counter resets.
When configuring the 'Max number of activities given per period', you can control how often an automation rule can give activities to a user. There are three period types: Days, Hours, and Lifetime.
DAYS - This option limits how many times the rule can give activities within a specified number of days (e.g., 1 day, 2 days, 3 days, etc.). When using 'Days', you must also choose how the day is calculated:
Time from the last execution - The countdown starts from the moment the activity was last given. Example: Max number of activities given = 2 times during 1 day, from last execution. If a user receives the activity twice, they can receive it again only 24 hours after the second time it was given.
Calendar days + UTC - The countdown is aligned with calendar days based on the selected UTC time zone. Example: Max number of activities given = 2 times during 1 day (Calendar days and UTC +3). After receiving 2 activities, the user can receive the next one after the next UTC +3 midnight.
Calendar days, user time - The countdown follows the user’s local midnight. Example: Max number of activities given = 2 times during 1 day (Calendar days, user time) After 2 activities, the user can get the next one after their next local midnight.
HOURS - This option limits how many activities the rule can give within a specific number of hours (e.g., 1 hour, 3 hours, 12 hours). Example: Max number of activities given = 1 time during 1 hour A user receives only one activity per hour. The next activity becomes available 1 hour after the previous one was given.
LIFETIME - This option limits how many activities a user can receive ever. Example: Max number of activities given = 50 times during lifetime Each user can receive up to 50 activities in total. After reaching the limit, they will never receive that activity again.
Last updated
Was this helpful?