Skip to main content

What's new

See the latest improvements and features in Talon.One here, or subscribe to our RSS feed.

January 2025

Allow rolling back active loyalty points​

Loyalty

You can now allow the deduction of active loyalty points when there aren't enough pending points in the customer's loyalty balance. This applies in the case of partially returned, cancelled, and reopened customer sessions.

Batch creation of loyalty cards​

Loyalty

You can now create batches of up to 20,000 loyalty cards directly in the Campaign Manager or using the Create loyalty cards endpoint.

You can also set the format for the loyalty card codes in your loyalty programs or in specific batches, and export them as CSV files.

Introducing session budgets​

Campaign Manager

Session budgets allow you to set a limit that targets each individual customer session. For example, you can control how much discount a campaign can give for each unique purchase. See Managing campaign budgets.

Introducing campaign staging and revisions​

Campaigns

This campaign feature introduces the Staged, Revised, and Pending campaign states. These allow you to stage campaigns for testing before activating them. Also, they allow you to revise active campaigns by applying independently tested changes to them. See Campaign staging and revisions.

Important: If you enable this feature for your Application, you cannot disable it later.

Assign Talon.One roles with SSO​

Roles & Permissions

We've enhanced our single sign-on (SSO) capabilities with a new feature for assigning roles to and removing them from Talon.One users directly from the identity provider.

You can currently assign Talon.One roles using Okta and Microsoft Entra ID as your identity provider.

More updates
Enhancements:
  • Loyalty:
    • You can now edit loyalty tier names in live loyalty programs that have point transactions.
    • Added loyalty program name and title properties to the responses of several loyalty card-related endpoints.
    • You can now enable subledgers in live loyalty programs that have point transactions.
    • The Generate loyalty cards endpoint now accepts a custom card identifier in the request and links the card to a specific customer profile if one is provided.
    • Loyalty card codes now support underscores _.
  • Dashboards:
    • Improved the UI for visualizing data in the Application dashboard. Users can now deselect data points in graphs.
    • Campaigns in the Application dashboard are now sorted alphabetically, making them easier to find.
    • Improved the UI for displaying data in all dashboards. Graphs now display the year when a user selects a time period that spans multiple years.
    • The Application dashboard now displays data about the influence of your campaigns on discounts from closed sessions and coupon redemptions.
  • Campaign staging and revisions:
  • Documentation:
  • Strikethrough pricing: General improvements to performance.
  • Integrations: Reduced the load time of the Integration API logs page.
  • Stores: Errors that occur when uploading stores via a CSV file are now displayed in a clearer format.
  • Campaign Manager: Improved the forms used to create and edit budgets.
  • Roles & permissions: Updated the Users section to distinguish Talon.One support users in production deployments and improve user identification.
  • SDKs: Updated the JavaScript, Java, C#, and Ruby SDKs.
Bug fixes:
  • Loyalty:
    • Fixed an incorrectly displayed subledger tier name in the Attribute Selector.
    • Fixed a bug that prevented the deletion of certain card-based loyalty programs after creating a batch of loyalty cards.
    • Fixed a bug that only returned profile-based loyalty program information in the responses of several Integration API endpoints.
    • Fixed a bug where exporting loyalty cards failed in certain scenarios.
    • Fixed a bug that prevented the sorting of loyalty cards by registration date in the Loyalty Cards tab of the customer profile overview page.
    • Fixed a bug that prevented users from recreating a customer profile with the same customer profile ID when the profile was in a loyalty tier before it was deleted.
    • Fixed misleading Recipient field behavior in the Add loyalty points effect in the Rule Builder.
    • Fixed a bug that rendered incorrect MAPI information about customer profiles linked to a card on the loyalty cards index page.
    • Fixed a bug that displayed a duplicated confirmation button on a loyalty program deletion modal.
    • Fixed a bug that caused customer profile information to load in card-based loyalty program settings pages.
    • Added a missing loyalty tier startDate property to the List customer data endpoint response.
    • Fixed a bug that allowed the Redeem loyalty points effect to be applied after the relevant campaign budget limit was reached.
    • Fixed a bug that prevented creating a subledger from the Loyalty Points tab of the customer profile overview page if the subledger ID contained a - character.
    • Fixed a bug that caused the loyalty member count to be incorrect in some cases.
  • Budgets:
    • Fixed an issue where the time period of budgets was inaccurately displayed in the campaign dashboard.
    • Fixed an issue where campaign budgets were not respected for some coupons.
  • Dashboards:
    • Fixed an issue where the Application dashboard did not include additional costs in calculations. The dashboard now takes into account additional costs for newly aggregated data.
    • Fixed a bug that prevented users from filtering Application dashboard data by campaign access group.
    • Fixed a bug where Avg. Items per Session on the Application dashboard displayed incorrect values.
    • Fixed a bug where only admin users could view the Application dashboard.
  • Catalogs:
    • Fixed an error that occurred when uploading a collection to a campaign created with a template that referenced a campaign collection.
    • Fixed a bug where the cart item catalog and customer session displayed inconsistent values.
  • Achievements:
    • Fixed an issue where a text placeholder looked like a predefined value in the achievements creation form.
    • Fixed a bug where achievements did not reset when the now parameter in a customer session was set to a time after the achievement reset date.
    • The Audit logs page now includes entries for deleted and updated achievements.
  • Attributes:
    • Fixed inconsistencies with how the product attribute name was displayed on the Attribute Selector, in cart item filters, and in cart item catalogs.
    • Fixed an issue where custom Application attributes did not load when they contained attributes of the type Location or List of location.
  • Strikethrough pricing: Fixed an issue where only the first 1000 campaigns were evaluated when generating strikethrough labels, as well as other issues that reduced performance.
  • Campaign Manager: Fixed an issue where it was not possible to update a revision in the Pending state.
  • Stores: Fixed a bug that prevented the cancellation of customer sessions if a campaign was updated to link to a specific store.
  • Cart item filters: Fixed an issue where the default Application cart item filter selection in the Rule Builder was not retained at the time of editing the campaign filters.
  • Campaigns: In Applications with Application cart item filters, it's no longer necessary to create a cart item filter to unlock the Rule Builder.
  • Strikethrough pricing notifications: Fixed an issue that affected notification batching for strikethrough pricing updates.
  • Management API: Fixed an issue where deleted customer data, specifically attributes, was not filtered by Application environment.
  • Campaign staging and revisions: Fixed an issue where it was not possible to recreate a testing API key after deleting one.
  • Coupons: Fixed a bug where coupon rejection reasons were not returned when a coupon campaign evaluation failed in the highest discount value evaluation mode.
  • Roles & permissions: Fixed a bug that prevented users with permission to create and edit draft campaigns from accessing the Rule Builder.