2026

  • 5 minute(s) read
Next

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

2026-04-10

Features

Release dates

  • Staging environment: 2026-04-09

  • Production environment: 2026-04-28

Customer import updates

New functionalities have been added to Customer imports.

  • Dynamic fallback values for date fields
    Dynamic expressions (e.g., now, first day of the month) can now be used as fallback values when importing customer data into the date-type attributes. These values are automatically parsed and resolved at the time of import, ensuring date fields with missing or empty values are populated with relevant, up-to-date data.
    Validation has also been improved, the mapping form now checks whether fallback values for date-type attributes can be parsed. Invalid inputs show a clear error, allowing issues to be identified and fixed to avoid import problems.

  • Reusable mapping configurations
    Customer import mapping configuration can now be exported and imported, making it easier to reuse setups or move them between environments. With the new option, configurations can be downloaded as a JSON file, and later upload it to quickly restore or replicate the same setup.

    After importing a configuration, the mapping interface is automatically pre-filled with the uploaded settings. The uploaded file is validated to prevent errors, and changes are only applied once explicitly saved.

Fixes

  • Fixed an issue in the Customer Insights menu where field names on the Events page were displayed as “0” instead of their actual names.

  • Fixed an issue in Shopify queue processing where missing or archived shops caused an unhandled exception and blocked further processing.

2026-03-18

Release date

  • Production environment: 2026-03-18

Klaviyo integration now supports OAuth authentication

API key usage has been replaced by OAuth access tokens, improving security and aligning with Klaviyo’s recommended authentication method.

New integrations can now be connected via a dedicated OAuth button instead of manually entering a private API key.

Existing API key–based connections remain supported.

In addition, a disconnect flow has been introduced, allowing you to safely and easily remove an active Klaviyo connection when needed.

2026-03-06

Features

Release dates

  • Staging environment: 2026-03-05

  • Production environment: 2026-03-31

Customer import now supports external ID matching

The recently introduced Customer imports functionality can now match and update existing records not only by Antavo customer ID, but also by external ID provided in the import file. This provides greater flexibility when syncing data from external systems where the external identifier is the primary reference.

Ometria integration update

An enhanced integration mode is now available for the Ometria integration, which updates only the customer data that has changed, instead of overwriting entire profiles.

Customer attributes are also sent in a more structured format, making them easier to manage and use for segmentation in Ometria.

The integration now also supports additional Antavo customer data, including tier information, expiring points, and multi-account balances (such as earned, spent, pending, reserved, and expired points per account). These fields can be selected in the integration settings and synced to Ometria, where they become available for targeting and personalization.

If you’d like to use the enhanced mode, please contact the Antavo Service Desk.

Fixes

  • Fixed an issue in the Checkout accept module where the auto_accept date parameter was not being automatically set.

  • Fixed an issue under the Events tab of customer profiles where event attribute names were displayed as “0” when adding a new event.

  • Fixed an issue with the /customers/{customer_id}/activities/rewards endpoint where the pagination incorrectly returned a next property when the limit query parameter equaled the number of available rewards.

  • Fixed discrepancies on the Dashboard where the reward claims chart did not align with the number of reward claim events listed in the event export.

  • Fixed an issue on the segment pages under Customer insights where the export button was not available.

  • Fixed an issue with the /customers/{customer_id}/activities/rewards/reward_id where fetching out-of-stock rewards returned a misleading error message.

  • Fixed an issue in Customer Imports where the customer attribute value mapping pop-up was displayed incorrectly.

  • Fixed an issue in Customer Imports where it was not possible to import multiple values for multiple-choice and select customer fields.

  • Fixed an issue in Customer Imports where the import queue processing was failing.

  • Fixed an issue in Customer Imports where clicking the start import button multiple times could initiate multiple import processes for the same import.

  • Fixed an issue in the Stores module where a store might not have been edited due to a validation error.

    The Store ID can now only be a lowercase or uppercase snake_case string.

  • Fixed an issue in Customer Imports where fallback values were not being imported correctly.

2026-02-06

Features

Release dates

  • Staging environment: 2026-02-05

  • Production environment: 2026-02-24

Extended data support at checkout confirmation

The checkout confirmation event (checkout_accept) can now submit custom attributes that were not present earlier, and can also set values for inherited attributes, if they were previously empty.

This allows adding or completing event data at checkout acceptance without changing the original checkout, making the integration more flexible while keeping inherited data consistent.

Fixes

  • Fixed an issue that might have caused delays in scheduled exports.

  • Fixed an issue in the Clubs module where, in certain cases, the club-update API endpoint could throw an error.

  • Fixed an issue in the Management UI where workflow elements overflowed the canvas space in Windows using Chrome.

  • Fixed an issue in the Expiring points module where already spent points could expire on the original expiration day.

  • Fixed an issue in the Stores module where a store might not have been edited due to a validation error.
    The Store ID can now only be a lowercase snake_case string.

  • Fixed an issue in the Contest lite module and under Customer insights where searching was not functioning properly.

  • Fixed an issue in the Prize wheels module where the slice time interval limitation was not correctly enforced in specific cases.

2026-01-09

Features

Release dates

  • Staging environment: 2026-01-08

  • Production environment: 2026-01-27

Async Events API

The Async Events API is now available for handling loyalty-related events with faster response times and more reliable processing.

Events such as customer updates, points adjustments, and checkout-related activities can now be submitted asynchronously and processed in the background.

This is especially useful during campaign launches, seasonal promotions, or flash sales, when high customer activity can generate a large volume of loyalty events in a short period.

By queueing and processing events asynchronously, delays and disruptions are reduced during peak activity. Events are tracked from the moment they are received, and if processing takes longer than expected, failed events are retained for analysis and can be reprocessed later.

Customer import improvement

A new Customer import option is now available in the Imports module, providing more control over the quality of customer data before it is added to the system.

Customer files can be uploaded and validated before import, with clear error feedback available when corrections are needed. File headers can be mapped to customer attributes, fallback values can be defined for missing data, and value replacements can be configured to ensure consistency.

This helps ensure that only clean, well-structured customer data is imported, reduces the need for manual corrections after import, and supports more reliable segmentation and customer communication.

Fixes

  • Fixed issues in the Insider module where an event might have triggered workflows multiple times, ensuring that each event only triggers one workflow instance.

  • Fixed an issue in the Trusted sites module where certain webhook requests to Emarsys failed.

  • Fixed an issue in the API signature check module where enabling the module caused an exception.

  • Fixed an issue in the Exports module so tier names can now be included in the export file.