☀️ Improved

• Goal Conversions Disabled for Multistage Campaigns

With this release, goal conversions will be temporarily disabled for multistage campaigns. This update introduces the following changes:

• The goal options will no longer appear on the campaign Setup tab when you create a new multistage campaign.
• The Performance tab in campaign Analytics will not be visible for these multistage campaigns.

This change applies only to new multistage campaigns and does not affect campaigns that are already active. The goal conversion feature will remain disabled for multistage campaigns while a long term solution is developed.

• SDK Attribute Management

When creating an attribute or tag, you can specify if an attribute can be updated using the Xtremepush mobile or web SDK. You can do this by enabling SDK Update for an attribute.

For more information, see Attributes & tags

• Journey Validation Improvement

To successfully save or launch a multistage journey, the configuration must satisfy the following criteria:

• Not start with a decision node.

• Include at least one delay or split node.

• Contain at least one action: message channel, ad retargeting, or promotion.

• Dynamic Promotions Improvement

The Dynamic Promotions UI is simplified so you only see the options that apply to your configured integrations, reducing configuration errors.

☀️ Improved

• You can now filter event triggers for event-triggered campaigns by using data contained within an array. To configure this, select one of the available Array operators from the property or value filters for the trigger event. For more information, see Use Array Filters for Event Triggers
• A warning message now appears at campaign launch if the specified trigger event, property, or value is incorrect or has not been recorded on the platform in the past year. For more information, see Event Validation at Campaign Launch in Event Triggers

🚀Added

• Audit Log for Consent Management

An Audit Log is available in Consent Management, which provides a detailed record of all changes made to consent preferences and custom consent channels. This log records the timestamp, action, who made the change, and a summary of the change.

For more information, see Audit Log for Consent Management.

• Rolling Segments Update

Rolling Segment calculations now time out after 5 minutes. If the calculation times out, the sync for that specific hourly cycle fails and an error message is generated.

For more information, see Rolling Segment Calculation Time Limit in Rolling Segments.

☀️ Improved

• When a consent preference is enabled in a single-stage campaign, you can now select any channel, not just those associated with the preference. For more information, see Validation in Single Stage Campaigns with Multiple Channels in Link Preferences to Campaigns
• In preference-triggered campaigns, you can apply additional filters to a consent preference using the Apply Filter toggle.
• For email campaigns with consent management enabled, you can now configure the List-Unsubscribe header to control whether users are unsubscribed from a specific preference, all marketing, or all email communications. For more information, see Consent Management and Unsubscribe Header in Email Content

🚀Added

• RCS Messages

In single-stage SMS campaigns, you can send text messages in a RCS (Rich Communication Services) format using the RCS toggle in the Content tab of your campaign. RCS message are currently only supported for users of the Vonage Gateway.

For more information on how to enable and use RCS messages, including delivery receipts, see RCS Messaging

• OTP Execute API

The OTP Execute API allows you to send pre-generated OTPs to your customers using Xtremepush’s SMS delivery functionality.

For more information, see the API documentation OTP Execute API

☀️ Improved

• A new toggle Block Multipart Messages, in the SMS settings page, allows you to prevent sending multipart SMS messages. When this toggle is active, an error message appears, preventing campaign launch if the SMS content exceeds 160 characters.

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

🚀Added

• Journey Builder 2.0[Beta]
  Journey Builder 2.0 is now available in Beta! It features a brand new user interface with improved navigation, better functionality, and expanded messaging channels.
  Journey Builder 2.0
  Journey Builder 2.0: Migration Guide
  Journey Builder 2.0: Webhook Channel
  Journey Builder 2.0: Event action

☀️ Improved

• Inline Preference Center – Onsite Consent Enhancements
  The Inline Preference Center for Onsite campaigns supports more compliant and flexible subscription capture flows. See Resubscribe users to SMS and email for more information.
• Language Translations for Email Preference Centre “Subscription Preferences
  You can customise the unsubscribe confirmation message in the Email and SMS Preference Centre for different languages, creating a fully localised experience. For more information on configuring these translations, see Translating System Generated Text
• Consent Management - Hit Event API endpoint
  Clients can now update consent_preferences directly via the Event Hit and Events Hit API endpoints, alongside events and attributes.

🚀Added

• SMS & Email Bot Click Protection
  The SMS & Email Bot Click Protection feature introduces advanced mechanisms to filter out automated bot clicks, ensuring a seamless experience for genuine users. This enhancement improves click tracking accuracy for SMS and email campaigns by preventing artificial engagement from security scanners and automated crawlers. For more details, please refer to our dedicated page.
• **Alerting system added for One-Time Password **This is a new alert functionality called 'Notify on Error' for our OTP integration. When enabled, this feature provides immediate email notifications regarding abnormal OTP behaviour, such as a high error frequency. For comprehensive details, please refer to our dedicated guide: One-Password Integration.
• **New One-Time-Password Export Methods **We've introduced new API endpoints and an export type to enhance OTP history retrieval and automation:
  • New API Endpoints
    Fetch OTP History Records List: Retrieve OTP history records with filtering and ordering options.
    Fetch OTP History Record Info: Get detailed information for a specific OTP record.
  • New Automated Export
    OTP History Automated Export: Enables scheduled exports of OTP history via email or file storage.

🚀 Added

• Prevent Multiple Journey Entries
  For recurring or triggered journeys, you can now prevent users from entering journeys they are already in or from journeys they have entered previously. Configure these settings in the Schedule tab for repeat and API-triggered journeys, and in the Event and Location tabs for other triggered types.
• One-Time Password
  The One-Time Password feature is designed to support secure authentication use cases, enabling seamless generation and verification of one-time passwords. This functionality includes:
  • Dedicated APIs: Easily send OTPs via SMS using the Generate API and validate user inputs with the Verify API.
  • Marketplace Integration: Customise OTP configurations and content directly in the platform.
    Step-by-step instructions and additional details can be found in the Quick Start Guide.
• Link Multi-Stage Campaigns with Consent Preferences
  Multi-stage campaigns now support using Consent Preferences during message sending. The selected consent preference for specific channels will be applied to campaign criteria, ensuring messages are sent only to recipients who meet the consent conditions.
• Additional Export Options for Consent Preferences
  You can now include Consent Preferences in manual, automated, and profile exports. This allows you to extract user consent data for deeper analysis and compliance reporting. Preferences are now available in: Segments and Profile Downloads.
• Goal Conversion Data for Variant Testing
  Goal conversion metrics are now calculated for each variant of a campaign, including the control group. View these metrics in Campaign Analytics > Engagement > Variant Testing.
• Traditional Chinese as a New Language
  Traditional Chinese is now available as a language option for multi-language single-stage campaigns.

☀️ Improved

• Support Nested Properties in Event Segmentation
  You can now create segments based on specific user interactions recorded in nested structures, such as $event.details.product.category.
• User ID as a New Column in Journey Actions Export
  The user_id column has been added to the Journey Actions export.

✅ Fixed

• The issue causing duplication of events in Data Manager has been resolved.
• An issue where users could save a campaign with a blank CSV for include/exclude segmentation has been resolved. A file must now be selected before saving.
• An issue preventing the display of goal conversion metrics on the campaign comparison chart has been resolved.

🚀Added

Linking Preferences to Single-Stage Campaigns
Single-stage campaigns now fully support consent preferences. You can link campaigns to specific consent preferences, ensuring compliance and improving targeting accuracy. Read More

☀️ Improved

• Active Users on Web Applications
  Data for active users' is now available for web applications. The data will only be available starting from the release date.

🚀Added

• Custom Input & Highlight Fallbacks - Email Content Preview
  It is now possible to provide custom input for dynamic content fields used in the email content under the new Custom Data tab under the Preview tab. Inputs will be automatically rendered in the preview.
  Dynamic syntax can now be highlighted in the preview. If a dynamic syntax returns fallback data or if a fallback is missing as a condition, these will be validated, and users will be informed in both the dynamic fields list and the rendered content. Read more
• Send yourself a preview - Email Content Preview
  This new feature allows you to send a preview email of the rendered version, helping you see how it would appear in your email inbox. Additionally, you can send the preview to selected recipients. It works for both single and multi-stage campaigns. Read more

✅ Fixed

• This fix prevents users from being able to to enable or disable variants in a campaign after it has been launched which was causing other issues. Variants will remain editable in drafts and campaign templates.
• Addressed an analytics timeout issue affecting campaign interaction data.