August 2022 Release Notes
SessionM platform release notes for August 2022 (release version 2022.5).
DETAILS
| Release to Staging | Release to Production | Release Version |
|---|---|---|
| August 1 - 3, 2022 | August 15 - 17, 2022 | 2022.5 |
No downtime is required for the release.
Customer Data Activation
Improvements for Customer Data Activation
Audience Generator - Improved performance of Audience Generator service by reducing the time to process entries, from ~40 million entries which used to take up to 24 hours down to 1½ hours.
Personalized Engagement
Improvements for Personalized Engagement
Catalog Picker Bulk Upload - We introduced a bulk upload feature to the latest version of our catalog picker in Campaigns. This means that you no longer need to manually select items when running a campaign with 1000+ SKUs.
Loyalty And Offers
Enhanced Point Tracing Option
We’ve introduced a new option to enable point tracing on the purchase offer flow by capturing the spend points reference to the User Offer, rather than to the Reward Store Offer. By doing this, it creates a reference that can be used to trace to the User Offer, which already provides traceability to the transaction where it was applied.
NOTE: Enabling this will change the data that is captured and will introduce a new Reference Type. Retroactively updating the data to reflect this is not part of this feature.
This option is disabled by default and can be enabled upon request to your Customer Success representative.
Improvements for Loyalty And Offers
Offers API - Enhanced the offer revoke flow by adding a return endpoint, api/2.0/offers/acquisition/return, that revokes an offer and returns the points when applicable.
Bug Fixes
Offers API
- Fixed a bug that significantly improved the average response time of both the
spend_points_multipleandpurchaseendpoints. - Fixed a bug that was causing the
get_user_offerendpoint to return an error when the point balance in the response payload was exceeding the int32 range. - Fixed a bug that was incorrectly allowing an active but expired
UserOfferto be locked by callingapi/2.0/offers/redemption/lock. - Fixed
fetch_bulk_offerendpoint so that it now has validation in place to- limit the amount of requested
offer_idsto 1000 and returns a 400 Bad Request error message with a suitable validation error instead of throwing a 500 Internal Server error with an unclear reason. - return a 400 Bad Request whenever a null
offer_idvalue is sent instead of throwing a 500 Internal Server error. - return a 400 Bad Request whenever an
offer_idempty value is sent instead of returning a 200 OK message.
- limit the amount of requested
Offers Date Format - Fixed a bug caused by the Issued Offer date format being different from the Redeemed Offer date format in the timeline. Both have now been unified to use the single format of YYYY-MM-DDTHH:MM:SS.MSZ.
Reward Store
- Fixed a bug so that the zero point reward store offers are now displayed in the
offers_discountresponse payload field, if they are applicable for the given transaction. This allows for perpetual use of offers without complicated issuance rules. - Fixed a bug where the
purchase_offerendpoint is now returning 400 instead of 500 when a user is denied access to the reward store.
Platform Wide
Improvements for Platform Wide
Data Privacy Forget Requests - Enhanced forget feature to better automate records request process across modules and data stores, including online and data cloud stores.