PEP v2.0 Release Notes
Our CRM has been undergoing significant transformation, in preparation to become part of the Gamanza Engage family of products. This involved migrating our CRM from the GamingGenius Platform and integrating it into the Gamanza Engage product line.
This transition required extensive effort, as we needed to remove several direct integrations from the Gamanza PAMS system. This change was essential to enable our CRM to function as a standalone product, enhancing its capabilities and expanding its reach to more customers.
Throughout this process, we've taken the opportunity to integrate, improve, and develop new features for our CRM platform. Here are some of the enhancements you can look forward to in the new Gamanza Engage CRM Version:
CRM Campaigns
Multi-Channel Support
You can now send communications via multiple channels at once for a single target group when creating a new Campaign. For example, you may choose to send both an email and SMS message to Group A and choose a different set of actions for Group B.

Multiple Channels are also supported in A/B testing.

New Delivery channel: Onsite Notifications
You can now relay important information to your customers through a new delivery channel called Onsite Notifications, which allows you to send web pop-ups to your players directly in your Casino UI, using rich media and template tools to direct personalized messages.

You can now use onsite notifications with the Multi-channel function to ensure your players don’t miss any important or urgent information, or to let them now about a new available bonus or pending reward. You can choose from a variety of template layouts:

Learn more about On-site Notifications here.
New Events Trigger API
We introduce a new Events trigger API that will now allow you to add new campaign trigger events automatically without requiring any additional development from the Gamanza Engage Team. For example, if you need to send a new trigger campaign for a new KYC process, you can simply contact your PAMS operator for them to send this new event and the event should then display automatically in our platform.
For more information, feel free to review our Open API technical documentation to learn more about this new feature: https://docs.gamanzaengage.com/docs/data-handling/trigger-events/index.html
Other additional features includes:
Delayed events: You can set a delay through the integration to send an event trigger campaign after a predefined amount of time.
Automatic Counters: If this property is enabled in the integration, the CRM will automatically begin tracking additional information regarding such activity (last event date and number of times the player triggered the event).
General stability improvements
New scheduling mechanism for scheduled campaigns
Better handling of errors
Better error reporting
CRM Budget Alerts and Caps
You can now define budget alerts (delivered via email) for external services, such as SMS or SendGrid, to have a more predictable monthly billing cost. You may also add a cap and stop the platform from sending messages to avoid going over your budget at the end of the billing cycle:

You can also manually select which phone numbers' country codes can receive SMS messages from you.
If a message is blocked by a cap or by a SMS country code restriction, this information will be displayed in the Analytics Section.
Templates Engine
New UI Redesign
All your templates have now been condensed into a single Templates section for easier access.

Segments - CSV Files using Email Addresses
When building a CRM Segment through a CSV file, it is now possible to upload a list of player email addresses, on top of using Player IDs.

Placeholder Filters
You can now apply render filters to your placeholders to change the way the data displays. For example, you can apply text capitalization, or specific data formats to date-based placeholders. You can apply these filters by adding a pipe character “|” to the filter function.
For example:
{{PlayersData.FirstName|capitalizeWords}}
If FirstName is john the render value should be “John”
{{PlayersData.FirstDeposit|date(format=MM/dd/yyyy)}}
If first deposit date is 2024-06-19T22:55:28.703+00:00 the render value should be “06/19/2024“
Player Engagement Player Card
New Player Card
There now is a dedicated player card specially designed with all your engagement tools for better handling of gamification features.

Custom Fields/Custom Metadata
You can now create additional player properties that do not exist in the PAMS to add more context and assign values directly in the Player Card. These properties can be useful for segmentation as well!

You can configure and create any custom fields through the Player Data section in the CRM and then assign values to each player directly in the Player Card.

For more information, please refer to the Custom Data manual here.
Other New Player Data Display
New design for current Player information stored in the CRM.

Campaign History Redesign

General Stability and Improvements
CRM Segmentation
New data aggregation models were specially developed to improve the time required to compute a segment, especially for complex operations like Activity Date Range with GGR, Net loss, gaming activity, etc.
There is also a new segment filter criteria for the loyalty program: you can now create segments based on the Token balance.
CRM Analytics
New data models and aggregations to improve analytics display and performance.
Last updated
Was this helpful?

