Smartico Help Center
Admin loginSmartico.aiTheAffiliatePlatform.com
  • Welcome
  • Products
    • 🔆CRM Automation
      • ◾Create Journey Flow
      • ◾Event Driven Journey
      • ◾Automation Rules
      • ◾Campaigns vs Automation Rules
      • ◾Segmentation
        • ▪️User State Segments
        • ▪️Behavioral Segments
        • ▪️Imported Segments
      • ◾Activities of Flows
        • ▪️Activity: Email
        • ▪️Activity: SMS, Viber and WhatsApp
        • ▪️Activity: Telegram Bot
        • ▪️Activity: Custom IM
        • ▪️Activity: WebHook
        • ▪️Activity: Limit
        • ▪️Activity: Add Points
      • ◾Communication channels
        • ▪️Email
        • ▪️Liquid Email
        • ▪️SMS, Telegram, Viber, and WhatsApp
        • ▪️Popups
        • ▪️Inbox
        • ▪️Push notifications
        • ▪️Content Variations
        • ▪️Opt-out & Communication Statuses
        • ▪️Gamification activities in the communications
      • ◾A/B Testing
    • 🎮Gamification Blocks
      • Setup steps and checklist
      • Points
      • Gems & Diamonds
      • Levels
        • Level Map
        • Levels Tips & Hints
      • Missions
        • Mission Types & Statuses
        • How to set up a Mission
      • Tournaments
        • Tournament Setup
      • Badges
      • Store
      • Example setup
      • Gamification UI skinning
      • Terms to protect
    • 🧠AI Models
      • ◾AI Enhancer
      • ◾Best Time Model
      • ◾Churn & LTV prediction
      • ◾Favorite product
      • ◾RFM Analysis
      • ◾Sport Recommendations
    • 🎲Mini Games
      • ◾Introduction to Mini Games
      • ◾Game template setup
      • ◾Custom skins for Mini-games
      • ◾Mini-games on the landing pages
      • ◾Using images instead of prize names in Spin the Wheel
      • 🏴‍☠️Treasure Hunt
      • ⚽MatchX Game
        • Creating Rounds
        • Resolution of a Round
        • Leaderboard
        • Game Statuses
        • FAQ: MatchX game
        • Loading MatchX & Quiz games on website
      • ❓Quiz Game
      • 🪂Prize Drop
    • 🗺️Lootbox 2.0
    • 🎁Missions Lootbox
    • 🏆Jackpots
    • 🎟️Raffles
    • 💡General concepts
      • ◾Bonuses
      • ◾Dynamic Rewards
      • ◾Custom Sections
      • ◾Attribution value
      • ◾Label tags
      • ◾Multi-currency usage report
      • ◾Multi-brands support
      • ◾Override translations on Label/Brand Level
      • ◾User markers (tags)
      • ◾Deep-links
      • ◾User roles in Back Office
      • ◾Email Gateways Guide
      • ◾"Client action" event
      • ◾Custom fields/attributes
    • 💻UI Widgets
    • ❔FAQs
      • FAQ: Gamification
      • FAQ: Data Studio & Reports
      • FAQ: CRM Automation
      • FAQ: Front-end integration
      • FAQ: Other topics
      • FAQ: Bonuses
  • Use cases
    • 🔆CRM Automation
      • ◾Cross-sell. Match users on different brands
      • ◾Mini-games usage in marketing campaigns
      • ◾Optimize Communication by excluding disengaged players
      • ◾Automated Sports Campaigns
  • Technical guides
    • ◾Integration process
    • ◾Front-end integration
      • ▪️Extended integration
      • ▪️Push configurations
      • ▪️Acquisition mode
    • ◾Data integration
    • ◾Bonus API integration
    • ◾Secured Messaging Gateways (Email/SMS/IM)
    • ◾Reverse integration
    • ◾Smartico Data Warеhouse
      • ◾Smartico DWH \ Affiliation views
      • ◾Smartico DWH \ CRM views
      • ◾Smartico DWH \ Gamification views
    • ◾Games catalog API
    • ◾Custom push gateways
    • Branded Links
  • More
    • 📝Release notes
      • 🌷May 2025
      • 🌷April 2025
      • 🌷March 2025
      • ❄️February 2025
      • ❄️January 2025
      • ⛄December 2024
      • 🍁November 2024
      • 🍁October 2024
      • 🍁September 2024
      • 🌞August 2024
      • 🌞July 2024
      • 🌞June 2024
      • 🌷May 2024
      • 🌷April 2024
      • 🌷March 2024
      • ❄️February 2024
      • ❄️January 2024
      • ⛄December 2023
      • 🍁November 2023
      • 🍁October 2023
      • 🍁September 2023
      • 🌞August 2023
      • 🌞July 2023
      • 🌞June 2023
      • 🌷May 2023
      • 🌷April 2023
      • 🌷March 2023
      • ❄️February 2023
      • ❄️January 2023
      • ⛄December 2022
      • 🍁November 2022
      • 🍁October 2022
      • 🍁September 2022
      • 🌞June 2022
      • ❄️January 2022
      • 🍁October 2021
      • 🌞July 2021
      • 🌷April 2021
      • ❄️February 2021
    • ⚙️Support Scope
    • 👍Request Demo
Powered by GitBook

More

  • expo.smartico.ai
  • ice.smartico.ai
  • play.smartico.ai

@ 2025 Smartico.ai

On this page
  • Overview
  • Real-time Automation Rule
  • Restrict Active Hours
  • Scheduled Automation Rule
  • Manually Stop a Scheduled Automation Rule

Was this helpful?

  1. Products
  2. CRM Automation

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 1 month ago

Was this helpful?

Overview

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 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:

  1. Segment - targeted users. For example:

  • All VIP Bronze customers

  • All customers with a deposit count > 1

  • Customers from Canada

  • etc

  1. 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

  1. 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.

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.

  1. Once-in-a-lifetime option - when enabled the rule will be executed only once for a specific user

  2. 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

  1. Activity type - what will be the action towards the player - give points, give bonus, give mission, start a campaign, etc.

  1. 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.

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 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:

Scenario
Behavior
Example

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

Here are some definitions of the available options for Scheduled Automation Rules:

  1. Segment - targeted users. For example:

  • All VIP Bronze customers

  • All customers with a deposit count > 1

  • Customers from Canada

  • etc

  1. 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.

  2. 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

  1. 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 manually stop the rule's execution. This option is located under the ‘More’ button and is only available when the rule is about to execute (5 mins 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.

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:

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/january-2022#automation-rules-based-on-the-value-accumulation
https://help.smartico.ai/welcome/more/release-notes/august-2023#scheduled-automation-rules
Example of Realtime Automation Rule Template in BO
Example of Scheduled Automation Rule Template in BO