June 2025

🚀Added

• Server Triggered In-App messages

A trigger option, Server Events, is available for On-site and In-App campaigns. This trigger option allows campaign messages to be stored in a queue when users are offline and displayed after they open the application or website. Automatic or manual polling can also be enabled for these campaigns, allowing real-time display of messages. 

For more information on server events and how to use them to trigger campaigns, see the following:

• Set Triggers for In-App and On-Site Campaigns

• Configure Server-triggered Messages

• Trigger Campaigns on Consent Preference Change

Campaigns can be triggered when changes are made to a user's consent preferences. With this feature:

• Messages can be sent to users notifying them of changes in their consent preferences.
• Users can be directed to multistage campaigns when their consent preferences change.

For more information, see Trigger Campaigns on Consent Change.

☀️ Improved

• A reauthentication error message is displayed on the project dashboard when Google or Meta exports fail because of expired access tokens.
• The inline preference center, in In-App modal and On-site pop-up campaigns, includes a mandatory age confirmation checkbox.
• For GiG’s PAM integrations, user subscription preferences can be added using GiG’s out-of-the-box integration. See Gaming Innovation Group (GiG) PAM for the supported GiG preference attributes. 
• IGT integrations support two additional events igtl_player_self_exclusion and igtl_player_self_exclusion_removal and one attribute igtl_self_exclusion_expiry
• IGT integration requires either E-Draw or Command configuration instead of both. 
• For OPAP integration in in-App campaigns, campaign and user IDs can be added to webhook payloads using pushCampaignId and  customerId.