Skip to main content

ES Loyalty Boost 2.9.1 release notes

note

This is a maintenance release to fix known outstanding technical debt issues and bugs.

What's in this release​

Fixes​

Slot-Level Audience Targeting Enhancement​

Fixed an issue with audience eligibility logic in the Boost loyalty offer campaign system.

Previously, when a valid audience (containing at least one member) was selected for targeting at the slot level, the system was not correctly applying inclusion logic. Campaign targeting now properly follows the required inclusion logic — members must be both included in the slot audience and included in the template audience of at least one offer template assigned to that slot.

This fix ensures more accurate audience targeting and prevents incorrect offer presentation, without requiring changes to existing audience configurations.

The fix also ensures that only audiences included in the Offer Pool or selected in Slots are considered during campaign processing. All other audiences in the program — including those created with invalid queries — are excluded from consideration.

See also:

Multi-Iteration Campaign Processing Fix​

Fixed a critical issue affecting campaigns with multiple iterations, where subsequent iterations were failing to generate the necessary files due to missing product and audience selectors.

The bug prevented campaigns from correctly transitioning to FILE_TRANSFERRED status after approval of second and subsequent iterations. All campaign iterations now correctly maintain their product and audience selector data throughout the approval workflow, allowing multi-iteration campaigns to run successfully with all required files generated and transferred to the loyalty system as expected.

This fix improves campaign reliability and eliminates the need for manual intervention when running complex multi-phase promotional campaigns.

String Escaping Fix in Snowflake Data Integration​

Fixed an issue where apostrophes in offer descriptions were being incorrectly double-escaped when data was inserted into Snowflake. This caused offer descriptions containing apostrophes to display with duplicate characters in the loyalty feed and promotions table, affecting the readability and presentation of offer content.

The fix ensures proper string handling during the data transfer process, maintaining single apostrophes in offer descriptions throughout the entire workflow from campaign creation to loyalty system integration.

Offer descriptions containing apostrophes now appear correctly in both the JSON files and on the loyalty side after campaign approval, eliminating the need for manual corrections or workarounds.