2025

📃 The detailed description of functionalities introduced by the Release notes are documented in the User Manual and Developer Documentation until the production release date. Make sure to revisit later on, or reach out to your Customer Success Manager if you have questions.

2025-07-04

This update does not include any new or modified Loyalty Engine features, as our team is currently developing larger functionalities to be introduced in upcoming releases.

Stay tuned for future announcements.

Fixes

Fixed an issue where the last login status incorrectly showed "Never" for users who had previously logged in.
Fixed an issue in the user group functionality, where users created without an assigned group were not automatically added to the default user group.
Fixed an issue in the Gamified Profiling module where profiling flows were incorrectly marked as complete when questions were reused across multiple flows.
Fixed an issue in the Stores module where stores appeared duplicated across pages and pagination did not display all stores correctly.
Fixed an issue in the Incentivized Purchase module where Special Earn Rules were not applied when the default percentage was set to 0%.
Fixed an issue in the Clubs module where the points_rewarded checkout attribute was not correctly handled for clubs using the split_points contribution type, causing pending point and refund inconsistencies.
Fixed an issue in Apple Wallet passes where two-level customer attribute placeholders (e.g., {customer.membership_id.0}) were not resolved.
Fixed an API error related to handling customer gender and country attributes during data synchronization with Salesforce Service Cloud.
Fixed an issue in the Instagram contests module where the customer’s Instagram username attribute was saved even when it did not meet the required validation criteria.
Fixed an issue where some refund events failed to process correctly for invitation-only tier structures.
Fixed an issue where refund events failed to process correctly when the Tier is enabled and configured with "invitation only" tier structures.
Fixed an issue in the Challenges module where creating a new challenge without specifying the criteria, start date, and end date caused an unhandled error instead of showing a proper validation message.
Fixed an issue in the Clubs module where the Club Member Remove Donation Intervals cron job failed to run properly due to incorrect data handling.
Fixed an issue causing delayed workflows to fail in certain cases where custom event attributes were used.
Fixed an issue in the Salesforce Marketing Cloud integration where editing a data extension was not available.
Fixed an issue in the Clubs module where the point donation limit didn’t apply when the Limit Reset Type was set to “The limit will not be reset.”

2025-06-06

Features

Release dates
Staging environment: 2025-06-05
Production environment: 2025-06-24

mParticle enhancements

Several enhancements have been introduced to the mParticle integration, improving configuration flexibility, data handling, and system transparency.

Error logging: A new grid view for inbound error logs has been introduced in the Management UI. This allows users to efficiently monitor and review error occurrences, offering a clearer and more organized way to track issues related to the mParticle integration.
Integration setup automation: Once the outbound connection (from Antavo to mParticle) is configured, the authentication token needed to establish the inbound connection (from mParticle to Antavo) is automatically generated and displayed on the integration configuration page of the Management UI. This automation eliminates the need for dependence on the Antavo team to provide authentication details, resulting in a smoother integration process.
Audience data syncing: A new Track audience data checkbox is available in the configuration page. When enabled, audience data sent from mParticle is processed to create, update, and remove customer lists and their members accordingly.
Selective identifier sync: A new Sync only configured identifier fields checkbox has been added to the Outbound Settings section. When enabled, only the selected identifier fields will be included in outbound payloads, excluding default fields like customer_id and email to prevent conflicts in third-party systems.

Point donation in clubs

The capabilities of the Clubs module have been extended by introducing a flexible manual point donation system. This allows users to donate points directly to clubs, providing an additional contribution method in addition to the existing automatic point contributions triggered by purchases or other events.

Administrators can configure club templates to support donations independently, in combination with automatic contributions, or as the sole method, depending on the desired setup. To maintain control and prevent misuse, donation limits can be configured, including minimum and maximum thresholds, as well as total donation caps per cycle.

To keep donation activities transparent, all point donations are logged as specific events in the customer’s event history.

These enhancements provide greater flexibility and control for clubs managing their point systems, supporting use cases where members manually contribute to a shared club balance.

Klaviyo SMS preference split

The Klaviyo integration now distinguishes between SMS Marketing and SMS Transactional channels when managing customer communication preferences. The previous unified SMS option has been split into two separate fields (SMS Marketing and SMS Transactional).

This change allows more precise control over how customers are subscribed or unsubscribed across different message types.

Webhook retry improvement

Webhook requests that reference a non-existent trusted site are now logged, allowing them to be retried once the configuration is corrected. This ensures better resilience in case of temporary misconfigurations.

Anniversary expiration flexibility

All date-type customer attributes, including custom and non-required ones, are now available for configuring anniversary-based point expiration. This change expands the flexibility of expiration settings. If the selected attribute has no value, the expiration date is calculated using the optin_at timestamp as a fallback.

Wallet token expiration control

A new Token Expiration setting controls whether wallet tokens expire after a configurable period or remain valid indefinitely.

When enabled, tokens expire after the set time, so expired download URLs become invalid. To get a valid download URL after expiration, a new request must be made to the wallet API endpoint, which generates fresh tokens on every call.

This change improves control over token validity and ensures users can always retrieve up-to-date wallet passes when needed.

Interrupt node enhancement

The existing Interrupt node has long allowed stopping all workflows affected by the same event, effectively halting the entire event processing.

Now, an additional option is available: the Interrupt Current Workflow node. This new node stops only the workflow it belongs to, without impacting other parallel or sequential workflows influenced by the same event.

This enhancement provides more precise control over workflow execution, enabling users to selectively halt individual workflows while letting others continue running.

Fixes

Fixed an issue in the mParticle module that caused crashes when processing certain data formats.
Fixed an issue where Dashboard charts displayed incorrect opt-in data in some cases.
Fixed an issue where regenerating charts led to overall data being overwritten with incorrect values.
Fixed an issue in the Quizzes module configuration interface where the answer translation pop-up became unresponsive.
Fixed an issue in the Imports module where importing opt-out events could get stuck, causing multiple customers to remain opted in.
Fixed an issue in the bulk reward claim operations where the system allowed the claiming of inactive rewards.
Fixed an issue in the Wallet module where pass configuration changes were not reflected on existing members’ Apple passes.
Fixed an issue where setting unique attributes to null may have resulted in a 500 Internal Server Error.
Fixed an issue in the Workflows module where workflows could fail if a Wait node was used with custom entities that didn’t match the expected structure during execution.
Fixed an issue in the Workflows module where workflows could fail due to a timing mismatch between the Wait node and custom entities.

2025-05-09

Features

Release dates
Staging environment: 2025-05-08
Production environment: 2025-05-27

Introducing the Antavo Promotion Engine

We’re introducing the Antavo Promotion Engine, a powerful new feature that brings flexible, real-time, API-first promotion management to every customer, not just loyalty program members.

The Promotion Engine allows marketers and developers to create, combine, and control promotions through a robust API and an intuitive user interface.

Capabilities include:

API-first and headless solution for seamless integration with POS, ecommerce platforms, pricing engines, and more.
Promotion logic and conditions can be configured via both a user interface and API, offering flexibility for campaign managers and developers.
Supports popular promotion types, including discounts, bundles, and free gifts, enabling users to build engaging, dynamic campaigns that drive conversion.
Fine-grained application and exclusion rules to define how promotions can apply together in a single cart.
Global-ready with tax and data compliance support.
High-performance engine, capable of handling 100,000+ requests per minute.
Can be used independently or integrated with the existing Loyalty Engine.

The Promotion Engine expands your toolkit beyond loyalty, making delivering impactful offers to every customer easier with reliable APIs and a promotion management interface.

Klaviyo enhancements

Improvements have been introduced to optimize the performance and reliability of Klaviyo communications, especially in workflows involving high-volume or time-sensitive customer interactions. These improvements include:

Klaviyo profile IDs are now leveraged where available, enabling faster and more direct customer identification during sync operations.
Update processes have been optimized to evaluate relevant customer data more selectively, improving API efficiency.
A queue mechanism has been introduced to batch list membership updates (e.g., add/remove actions), enhancing stability and performance in larger-scale workflows.
A dedicated workflow node is now available to manage subscription status changes (subscribe and unsubscribe), independent of list membership.

These updates support smoother and more scalable integration with Klaviyo, improving performance in scenarios such as reward introductions, tier transitions, and time-based campaigns.

Webhook performance improvements

To improve the performance of outgoing webhook traffic, we’ve introduced new settings to help you control how requests are processed. Performance can now be fine-tuned to avoid potential bottlenecks and optimize traffic.

We’ve added a new section under the Trusted sites module, where two key configuration options can be adjusted:

Maximum number of requests per second (RPS)
Number of asynchronous threads handled simultaneously

These settings help optimize performance by giving control over the rate of request processing, ensuring smoother integrations and better performance.

Fixes

Fixed an issue where bulk reward claims got stuck in processing if the callback URL was missing or invalid.
Fixed an issue where suspending a loyalty member did not block them from spending points.
Fixed an issue in the mParticle integration to ensure point-changing events are sent in the correct order, so synced updates reflect the correct point balance changes.
Fixed an issue with the event synchronization from Antavo to mParticle, where the mParticle customer identifier was placed incorrectly in the sync request. It is now included in the user_identities array, ensuring proper connection of customer data with mParticle.
Fixed an issue in the Clubs module where the "&" sign did not display correctly in the club name after saving.
Fixed an issue where the completion time didn’t appear on the Job log page after a cron job finished.
Fixed an issue where customer information with a zero ("0") value was incorrectly shown as empty in the Personal Information section on the Customer Overview page.
Fixed an issue where translatable reward category texts were not returned in the requested language when accessed through the API.
Fixed an issue in the Rewards module where incorrect expiration dates for claimed and unclaimed rewards were caused by time zone handling errors during coupon updates.

2025-04-11

Features

Release dates
Staging environment: 2025-04-10
Production environment: 2025-04-29

Management UI interface update

Starting April 29, the Antavo Management UI will have a refreshed look, including updated colors, fonts, and module logos. While the visual design has been modernized, all features and functionalities remain the same.

No action is needed — the update will be applied automatically, and the Management UI will continue to work as usual.

Trusted sites module update

The Trusted Sites module has been extended with two new authentication methods to improve security and facilitate server-to-server communication.

Standard OAuth 2.0 Authentication (RFC 6749): This method enables secure authentication and authorization of requests between systems, suitable for machine-to-machine scenarios without user context.
OAuth 2.0 JWT - JSON Web Token (RFC 7519): This token-based method streamlines authentication and authorization, facilitating efficient interactions with external systems.

These updates enhance the security and flexibility of the Trusted Sites module. The existing OAuth 2.0 option remains available for users.

Clubs module update

Until now, only one club template could be active at a time within the Clubs module.

This limitation has now been removed, and multiple club templates can be active simultaneously. This change enables more flexible club management, making it possible to test different formats or run several club mechanisms in parallel without deactivating existing templates.

Fixes

Fixed an issue to improve the response time for the reward claim API endpoint of the Display API.
Fixed an issue in the Challenges module to ensure the challenge progress calculation accounts for the start date setting.
Fixed an issue in the Quizzes module to ensure successful completion of quiz API requests.
Fixed an issue in the Exports module where the aggregated coupon export failed.
Fixed an issue in the Wallet module to ensure the tier expiration date updates are accurately reflected on wallet passes.
Fixed an issue where the workflow name with hyperlink did not appear for customer list-related events in the customer event history.
Fixed an issue in the Rewards module to enable users to copy and paste text into the Description field for rewards when adding translations.
Fixed an issue where inconsistent error messages were returned when sending an API request to redeem an expired coupon.
Fixed an issue in the Offers module to ensure timely offer availability.
Fixed issues related to deleting mapping fields in the Insider integration configuration.
Fixed pending points handling in the Multi-account module to ensure accurate calculations and prevent negative pending point values during checkout updates.
Fixed discrepancies in mapping mParticle purchase actions to Antavo checkout and checkout_item events in the mParticle integration.
Fixed an issue in the Prize wheels module to ensure the prize wheel spin repeat interval only affects the specific prize wheel it is set for.
Fixed an issue in Workflows where workflows did not complete their execution after the wait node in certain cases.
Fixed an issue in the Multi-account module where, when negative balance was enabled, point_spend events could not be submitted if they would result in a negative balance.

2025-03-07

Features

Release dates
Staging environment: 2025-03-06
Production environment: 2025-03-25

Insider integration

The integration between Antavo and Insider is now available, enabling the seamless synchronization of customer profile data and events from Antavo to Insider.

Data mapping can be configured to define the corresponding customer fields, events, and event fields between Antavo and Insider.

The synchronization runs continuously in the background, providing real-time updates from Antavo to Insider. The history of data synchronization and any errors that may occur can be tracked through the logs, ensuring transparency and facilitating troubleshooting.

Future releases will enhance this integration by adding two-way synchronization capabilities, further improving data management and utilization across both platforms

Coupon management improvement with API endpoints

New API endpoints are now available for the Coupons module, enabling coupon pool management and importing coupon codes into uploaded coupon pools. This enhancement supports more efficient management of coupons and streamlines operations.

Batch uploads: The endpoint allows the upload of coupon codes in batches while filtering out duplicates.
Flexible assignment options: Coupon codes can be assigned to specific customers, new coupons can be created for non-existent ones and linked to the specified customers, and existing coupons can be unassigned as needed.
Progress tracking: The progress of uploads can be tracked, and detailed error information for any failed uploads can be retrieved.

Fixes

Fixed an issue storing Twilio Segment external customer IDs in inbound logs for proper customer linking.
Fixed an issue where the Completions tab under the Challenge module failed to load data.
Fixed an issue in the Rewards module where generic coupon codes could not be redeemed when unassigned codes were present in the coupon pool.
Fixed an issue where start and end dates in the Offers module were incorrect due to day differences between local time zone and UTC.
Fixed pending points handling in the Multi-account module to ensure accurate calculations and prevent negative pending point values during checkout.

2025-02-07

Features

Release dates
Staging environment: 2025-01-06
Production environment: 2025-02-25

Clubs module upgrade

The Clubs module, first introduced in the previous release, has been further enhanced with new capabilities, including point expiration handling, refund management, enhanced statistics, and club detail changes. These improvements provide better control over club points, streamline financial accuracy, and offer deeper insights into club activity.

Point expiration logic: Club points can now be configured with expiration dates, automatically moving unused points to an expired balance. With API support for tracking upcoming expirations, businesses can better manage point liabilities while encouraging timely member engagement.
Refund management: New functionality enables point refunds related to both earning reversals and reward revocations. When a transaction is refunded, club points decrease accordingly. If a redeemed reward is revoked, points are returned to the club’s balance. This provides a clearer, more predictable experience for both program operators and members.
Enhanced statistics page: The Club Details page now includes real-time charts and key metrics, such as member count, point balance trends, and average customer contributions. These data-driven insights help track engagement, identify trends, and fine-tune strategies for maximizing club participation.
Handling club detail changes: For flexibility, club names can now be edited post-creation through the Management UI and API, with customizable user restrictions on name changes.

By improving point lifecycle management, refining refund processes, and providing deeper analytics, these enhancements strengthen the Clubs module as a powerful tool for fostering engagement and collaboration among loyalty program members. Future updates will continue expanding these capabilities to further enrich the experience.

Historical transaction import update

Exception error messages related to historical transaction imports have been updated to align with established error message standards. More informative messages help users quickly understand issues and take appropriate steps to resolve them.

Twilio Segment integration enhancement

The Twilio Segment integration has been improved with a more secure authentication method for requests sent from Twilio Segment to Antavo. This enhancement ensures a stronger and more reliable verification process for data exchanges between the two systems.

Fixes

Fixed an issue where spend-based tier progression was not updating correctly in the Management UI.
Implemented advanced mapping for checkout items in incoming mParticle API requests to Antavo, allowing proper processing of multiple items sent.

2025-01-10

Features

Release dates
Staging environment: 2025-01-09
Production environment: 2025-01-28

Twilio Segment integration

Antavo now integrates with the Twilio Segment customer data platform (CDP), allowing a bidirectional synchronization of both customer and event-related data between the two systems.

With this integration, businesses can keep their customer data up to date across both platforms seamlessly, ensuring accurate and comprehensive customer profiles and facilitating the creation of personalized experiences using loyalty-related data.

Clubs module

The Clubs module is now available in the Loyalty Engine to enhance loyalty programs by promoting group participation and shared engagement. Two key capabilities are included in this release:

Group Management
- Create and join Clubs: Clubs can be created using templates configured by business users in the MUI interface. Loyalty members can join or leave Clubs and invite other members to participate.
- Controlled setup: Templates enable the definition of specific rules and behaviors for each Club.
Earn and Burn Points
- Shared point management:
  - Earn points: Members can accumulate points collectively into the Club account.
  - Burn points: Members can redeem points from the Club balance for rewards.
- Template-driven rules: The rules for earning and burning points can be configured through the Club template settings.

All Club functionalities are accessible via API, supporting seamless integration with external systems.

The Clubs module introduces a framework for collaboration among loyalty members. In the near future, the feature will be expanded with additional functionalities to provide even greater flexibility and value.

Shopify integration update

In the Shopify integration, the handling of customer email address modifications has been improved.

If the Primary ID used for data transmission between Antavo and Shopify is the email address, this update ensures that any changes to a customer's email in Shopify are automatically updated in Antavo. This prevents conflicts between the two systems and ensures customer data remains accurate and consistent during processing.

Coupon import update

In the Imports module, an important update has been made to the coupons model to enhance the handling of required attributes during the coupon import process. This update provides a solution for managing required attributes regardless of whether a coupon pool is used for rewards or if coupons are defined directly through the reward settings. Attributes related to coupon distribution are now marked as required, reducing the risk of errors during the import process by ensuring that all necessary information is clearly indicated.

When coupon pools are used: A pool selection is required, either from the dropdown or within the import file.
When coupons are defined within the reward settings: The parent field (reward ID) becomes mandatory to link the coupon to a specific reward.

mParticle integration enhancements

Enhancements have been made to the mParticle integration:

Two new outbound setting fields have been added to the mParticle configuration interface in the Management UI. These fields enable mapping between Antavo customer attributes and mParticle identifiers, ensuring accurate and seamless data integration.
The mParticle integration now supports customer currency synchronization.

Fixes

Fixed an issue where checkout requests were properly handled, but an error message was occasionally returned.
Fixed an issue where the filters for a customer’s export changed to a different setting upon completion.
Fixed an issue where events were registered for failed transaction imports.