User GuideGamification GuideDeveloper GuideAPI Reference
User Guide
Xtremepush.com

Platform releases 2026

June 2026

12/06/2026


🚀 What's new?

  • Content Preview

You can now preview campaign content for in-app, mobile push, and inbox campaigns. Previously, this was only available for email campaigns.

🚧

Sending a test preview is currently not available for inbox campaigns.

For more information, see Preview your Campaign

  • Email Pre-header

You can now add a pre-header directly in the email campaign builder using the new Preheader field. For more information, see Adding a preheader text to your email

☀️ What's improved?

  • You can now use a decision node as the starting point of a multistage journey.

  • A Global unsubscribe option toggle is now available under Channels > Email Settings. Use this toggle to control whether the Unsubscribe from all option appears on your email preference center page.

    The toggle is enabled by default for existing and new projects, meaning the Unsubscribe from all option remains on your preference center page. For more information, see Email Settings.

03/06/2026

🚧

Deprecation Notice

  • App Tokens: App tokens will not be available on projects created after the June 2026 release. They will be removed for existing projects in a future release and we will notify you in advance when this happens.
    • If you have existing projects using app tokens, we recommend beginning migration to OAuth 2.0.
    • New projects must use OAuth 2.0 to authenticate External API requests.
  • OAuth 2.0:
    • The previous method of passing a JWT directly as Authorization: Bearer <jwt_token> is deprecated and will be removed in a future release.
    • GET requests to the /token endpoint will no longer be supported in a future release.
    • We will notify you in advance before these changes take effect.

Additional changes have been made to OAuth 2.0, see OAuth 2.0 Updates below for more details.

For more information, see:

🚀 What's new?

  • Synced Rows

You can now save any row in the email builder as a synced row, which can be reused across campaigns and templates within the same project. When you edit a synced row, the update is automatically applied to every campaign and template that uses it.

For more information, see Synced Rows.

  • Data Retention Settings

You can now configure data retention settings directly in the Xtremepush UI, controlling how long uncontactable user profiles and audit log records are retained on the platform before they are automatically deleted. Only users with a Provider Admin or Company Admin role can change the data retention settings.

See Data Retention for more information.

  • Player Eligibility Check Integration

The player eligibility check integration allows you to verify each player's exclusion status against a national regulatory body before a campaign is sent, ensuring that players who have self-excluded do not receive campaigns.

See Player Eligibility Check (ComeOn) for more information.

☀️ What's improved?

  • OAuth 2.0 Updates
    • The OAuth 2.0 token endpoint now supports client_credentials grant type in addition to the existing jwt-bearer grant type.
    • The lifetime field can be included in the request to control how long the returned access token remains valid in seconds, up to a maximum of 86400.
    • Public key uploads now support both X.509 certificates and SPKI public keys.

See OAuth2.0 authentication for more information.

  • JB 2.0 Improvements
    • iOS and Android push channels are now consolidated into a single Mobile push channel in Journey Builder 2.0, matching the behaviour in Journey Builder 1.0. You can use the toggles on the Setup tab to select which platforms to send to.
    • You can now use Copy from to replicate content between languages and push channels when setting up multi-language Mobile push and Web push messages.
  • Campaign analytics for RCS messages now includes Open Rate, showing the percentage of delivered messages that recipients opened.

April 2026

🚀 What's new?

  • Journey Builder 2.0 Enabled by Default

Journey Builder 2.0 is enabled by default for any new projects created after the April 2026 release. The beta label has been removed from Journey Builder 2.0, and Journey Builder 1.0 is no longer available as an option when setting up a new project.

No further updates will be made to Journey Builder 1.0 after this release. If your project is still using Journey Builder 1.0, we recommend beginning migration of your campaigns to Journey Builder 2.0. See our Journey Builder 2.0: Migration Guide for more information.

Journey Builder 1.0 will be deprecated in a future release, and we will notify you in advance when this happens.

  • In-App Channel in Journey Builder 2.0

You can now include in-app messages as a channel node within your multistage journeys. When a user reaches the node, the message is queued on the server and displayed the next time they open the app.

See Journey Builder 2.0: In-App Channel for more information on the in-app node.

  • Dynamic Content in API-Triggered Multistage Campaigns

Multistage API-triggered campaigns now support dynamic content. You can pass attribute values using the Campaign Execute API and reference them across all message nodes in the journey.

See Dynamic Content in API-triggered Multistage Campaigns in API triggered campaigns for more information.

☀️ What's improved?

  • Journey Builder 2.0 improvements

    • You can now use Copy from to replicate content between languages when setting up multi-language push and inbox messages, matching the behaviour already available in single-stage campaigns.
    • Inbox message content, including images and payload options, can now be configured individually per language.
    • Journey Builder 2.0 includes significant performance improvements, making it more scalable and reliable for high-volume campaigns.

  • The Service ID for your OTP integration is now displayed on the Overview tab of the integration. This removes the need to extract it manually from the browser URL when making Generate and Verify API requests.

  • You can now customise the placeholder text shown in the email input field of the Inline Preference Center using the Email Placeholder Text setting. If left blank, it defaults to "Enter Email Address".

    See Contact Field in Resubscribe users to SMS and email for more information on the Email Placeholder Text setting.

  • Additional GiG customer profile attributes are now available in Xtremepush, covering Marketing & Tracking, Customer Verification & Location, A/B Testing, Responsible Gaming, and Customer Segmentation.

    See Gaming Innovation Group (GiG) PAM for the updated list of supported attributes.


March 2026

🚀Added

  • API Scopes and Permissions

Specify scopes for each Client ID to provide granular access to the Xtremepush APIs that your team or external systems interact with.

These scopes are only available for integrations that use OAuth authentication. By assigning specific scopes to a Client ID, you ensure that an external system only has the permissions required for its specific task.

Go to Settings > Integrations > API Integrations to set scope for each client ID. See API Scopes and Permissions for more information.

  • Preference Based Dynamic Content

Create dynamic content that displays different campaign messages to users based on their specific consent preferences. This allows you to tailor your messaging by showing content only to users who have opted in to certain preferences.

You can insert the consent preference icon directly into the campaign message editor. Use Twig logic to set conditional rules that determine which content is displayed to each user. See Preference Based Dynamic Content for more information.

  • Segment Export API

Export device or profile data from segments created in your project by using the Segment Export API. Two new endpoints have been introduced to support this workflow.

You must use OAuth 2.0 authentication and ensure your Client ID has the Export and File Download scopes enabled. See Trigger Segment Export and Download File by ID for more information.

☀️ Improved

  • Attribute names are automatically validated when you create them manually or through the API. This validation is enabled by default but can be disabled by contacting Xtremepush Support.
  • You can rearrange the order of Inline Preference Center options, like Age Confirmation and Terms and Conditions, as per your requirement.
  • A validation error appears if an attribute type and its selected operator do not match, preventing you from saving an invalid segment. This error also appears on previously saved segments that were already non-functional, allowing you to identify and correct the logic.
  • On the Analytics tab of a multistage journey, the Journey Actions section displays status messages. When you first view this section, a message informs you that the platform is processing your campaign data. If the campaign data is not retrieved within five minutes, a Failed to get journey action stats message appears.

January 2026

☀️ Improved

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

  • 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.
  • The Dynamic Promotions UI is simplified so you only see the options that apply to your configured integrations, reducing configuration errors.