Version 2.52
See what's included in our release version 2.52
Monthly Deposit Potential (Player Feature)
Introducing a new data model, Monthly Deposit Potential. This is now available as a Player Feature in the back-office. This model redefines Player Value by estimating how much a player is capable of depositing monthly, rather than relying solely on recent activity.
Players are automatically segmented based on their Monthly Deposit Potential score:
π Platinum β Highest deposit potential players (50% of total Monthly Deposit Potential).
π₯ Gold β High deposit potential players (25% of total Monthly Deposit Potential).
π₯ Silver β Moderate deposit potential players (15% of total Monthly Deposit Potential).
π₯ Bronze β Lower deposit potential players (10% of total Monthly Deposit Potential).
Make sure to read the full documentation around this Player Feature here.
β¨β Micro-features and improvements
The default time period set on the Player Timeline has been changed to 7 days
SDT Activities now displays a warning in case the time of the Trigger is within 5 minutes of the current time. This ensures that there is sufficient time for the system between enabling and the Activity being fired
Action Builder - Cloning an Action Group immediately puts it beside the original Action Group and becomes the active tab
Importing Action Groups should now be processing faster
Improved UX for assigning Origins to email templates
When creating a new Action Group a new tab is created and immediately focused on
πβBug Fixes
The full name of all Action Types is now visible within the Activity Builder
We have fixed a bug in Activities where it sometimes warned about unsaved changes incorrectly
Users with read-only access should no longer be able to add a Scheduled Action in an Activity
Activity ID is now displayed immediately when creating a new Activity
Resolved an issue where the icons within the Rich Text Editor would not fit within the container
HTML is now supported in On-Site Notification Title Placeholders
The counter for the amount of Segments using a Smart Segment now loads correctly
Last updated
Was this helpful?