Help CenterA communication-free journey is an automation setup that does not involve any direct communication with the customer. Instead, it operates entirely in the background, triggering internal actions, data updates, or integrations based on predefined conditions.
These journeys are particularly useful for:
✅ Rewards processes - allocating loyalty points, experience levels or granting rewards.
✅ Compliance and security monitoring – Flagging suspicious transactions, enforcing KYC/AML requirements, or logging regulatory events.
✅ Data synchronisation and enrichment – Updating CRM custom attributes, customer tagging, syncing customer events with external platforms, or triggering webhook calls.
✅ Notification automations – Notifying support agents or VIP managers.
✅ Suggested read: Setting up VIP Monitoring.
Allocating Experience Levels Based on Wagers Won
In this example scenario, customers are awarded 1 point for every Sportsbook wager won.
The trigger is activated instantly upon a Sportsbook payout, with no participation restrictions. Each time a payout event occurs, the automation journey is automatically triggered.
By utilising a data operation, a custom attribute called ExperienceLevel can be created and configured to accumulate points each time the journey is triggered. Instead of replacing the existing value, the configuration is set to increment the attribute by 1, ensuring that ExperienceLevel continuously tracks and updates the customer's engagement over time.
Referencing the custom attribute in a webhook allows the CRM to update a third-party system with the total points accumulated for the customer.
✅ Suggested read: Webhook Variables section in Connecting a Webhook.
Monitoring Large Deposits and Assigning AML Flags
In this scenario, any deposit exceeding 5,000 will trigger the automation. The deposit amount is stored in a custom temporary attribute, an AML flag is set to true, and a Webhook request is sent to the Player Account Management (PAM) system for further processing.
The trigger is activated instantly when a customer makes a deposit exceeding 5,000. There are no participation limits, meaning the trigger will fire after every qualifying deposit.
Enabling the "Enable variable with name" option allows the Data Operation block to retrieve the event value for further processing. Additionally, setting the advanced condition to deposit state = success ensures that the trigger only activates for successful deposits, preventing false activations from failed or pending transactions.
While the above trigger is activated based on a single event value, additional options are available to activate the trigger based on lifetime or journey accumulated event values.
✅ Suggested read: Lifetime versus Journey Accumulated triggers.
Create a new custom attribute named LastLargeDeposit using the Data Operation block. Assign the deposit variable to this attribute, ensuring that it replaces the previously stored value without using increment, so that only the most recent qualifying deposit is recorded.
Multiple Data Operation blocks can be chained together for sequential processing. In the next Data Operation, a new custom attribute of type boolean, named AML, is created. A true value is then assigned to this attribute, indicating that the AML flag has been triggered.
Finally, referencing the custom attributes in a webhook allows the CRM to update a third-party system with the deposit value and AML flag.
✅ Suggested read: Webhook Variables section in Connecting a Webhook.
Enriching Customer Data with Tags
The Tag block in Journeys allows for dynamic customer segmentation by assigning labels based on real-time interactions. This enhances data organisation, automation, and targeted engagement.
Use Cases for the Tag Block
- VIP Tracking – Automatically tag customers as VIP when their total deposits exceed a threshold.
- High-Risk Behaviour – Assign an AML tag to customers making suspicious high-value transactions.
- Product Interest Identification – Tag customers based on their preferred betting category (e.g., Casino Player, Sportsbook Bettor).
- Churn Prevention – Apply a "Dormant Player" tag when a customer has been inactive for X days.
- Loyalty Program Tiering – Upgrade customers to Gold, Silver, or Bronze loyalty tiers based on wagering activity.
- Responsible Gaming Alerts – Tag players who exhibit increasing bet frequency or high consecutive losses.
- Customer Journey Optimisation – Mark customers who engage with specific promotions, allowing for better retargeting.
By leveraging tags, operators can create more granular segments, automate personalised actions, and streamline customer management.
ℹ️ Tags can be used as segment attributes in the Segments UI or via Natural Language Queries in Betintel.ai.
Assigning a Tag
When editing the Tag block, click on the dropdown menu to select an existing tag or manually enter a new tag name and click Add. Note that the dropdown will only display tags that have already been used within the current journey.
Once added, select the VIP tag and choose an operation:
- Add – Assigns the tag to the customer.
- Remove – Unassigns the tag from the customer.
Other samples
Several other samples using the data operation block:
- Adjusting a Deposit-Based Bonus
- Setting a High-Value Transaction Flag
- Setting a High-Value Transaction Flag
- Setting Progressive Reward Levels
- Setting Progressive Deposit Bonuses
- Assigning VIP Levels Based on Lifetime Values
✅ Suggested read: Applying Mathematical Calculations with Data Operation Blocks.