User GuideDeveloper GuideAPI Reference
User Guide
Xtremepush.com

Platform releases 2025

Learn what's new on the platform

Suggest Edits

July 2025

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

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:


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

April 2025

v.2025.3

🚀Added

☀️ 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.

March 2025

v.20205.2

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

January 2025

v.2025.1

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

Updated about 1 month ago