January 2023 Release Notes
SessionM platform release notes for January 2023 (release version 2023.1).
DETAILS
| Release to Staging | Release to Production | Release Version |
|---|---|---|
| January 10 - 12, 2023 | January 24 - 26, 2023 | 2023.1 |
No downtime is required for the release.
Customer Data Activation
Revised and Updated Tabs in the Insights Module
Following the update on the Campaigns tab in the October release, we’ve updated and improved the information available on the remaining tabs in the Insights module. The new tabs inform decisions regarding offer setup and provide an overview of point economies and the general health of loyalty programs.
Key improvements include:
- Membership overview, including new members over time, tier-based purchase recency, average order value, average revenue per user and transaction frequency.
- Sales breakdowns per current loyalty tier, payment type and payment channel.
- Overall sales compared to transaction count and purchasing members over time.
- Offer overview, including total offers issued, redeemed, expired and revoked; offer liability up to a selected date or over time.
- Points overview, including total points issued, redeemed, expired and revoked; point liability up to a selected date or over time.
- Filtering of visuals by offer (for the Offers tab), tier (for the Incentives tab) and date range (for all tabs).
You can find the updated documentation for this change in our SessionM Help Center.
Salesforce Service Cloud, Erie, Version 2.6
Enhancements:
- We implemented a retry mechanism for API requests to the SessionM Platform that receive server errors (5xx). The service re-tries the failed requests again before marking them as failed, to solve random partial failures and short-lived transient failures. The number of retry attempts and the delay between retries is configurable in the package settings page. This service applies to:
- User interactions with the SessionM Loyalty Package Lightning Web Components for making updates to a customer’s profile, points balance, offer wallet, etc.
- Automatic syncing of Account or Contact records to SessionM customer profiles
- Improved user experience on the Salesforce mobile app
Fixes:
- Restored the missing Configure link in the Installed Packages setup view
- Fixed a bug that displayed all redeemed and expired offers in the respective components when the customer sync failed
- Improved the handling of Customer Lifetime Value data to prevent customer sync failures when some of the values were returned as strings instead of numbers
You can see the updated Salesforce Service Cloud guides in our documentation center.
Personalized Engagement
Improvements
Salesforce Marketing Cloud (SFMC) Journey List Expansion - Increased the number of SFMC journeys that the Campaigns module can display from 50 to 100. This enables clients with many journeys active in SFMC at once to continue to create campaigns in SessionM that can initiate them based on loyalty triggers.
Bug Fixes for Personalized Engagement
SKU Behaviors in Campaigns Templates - Fixed a bug where Behavior templates would not save the Categories or Items selected in a SKU restriction. Now, clients can save time by templatizing behaviors when they frequently include or exclude the same set of products in their promotions.
Loyalty And Offers
Display Runtimes for Points Expiration and Tier Maintenance Jobs
Time zone differences can cause confusion regarding when points expire and when tier maintenance is run. A new enhancement displays when each of these jobs runs.
In the Point Management module, the runtime for the point expiration job is shown under the dropdown for selecting the point expiration policy.

In the Economy Rules module, the runtime for the tier maintenance job is shown in two places: the program overview page in the tier maintenance section and on the frequency section under Enable Maintenance.


More Accurate Display of Points Balance – On Demand Point Expiration
Until now, the end-of-year point expiration job could take several days to complete. While the job is running, the point balance for a specific customer could be inaccurate, allowing them to redeem points that should have been expired. To address this problem, when a customer inquires about their point balance, we have created a new service that checks if the point account is due for expiration. If expiration is due, the job runs before returning the point balance, ensuring that an accurate balance is returned.
Bug Fixes for Loyalty And Offers
Reward Store - Fixed an issue that prevented client implementations using Olo middleware from redeeming zero-point reward store offers.
Offer Create API - Fixed an error with the Offer Create API that allowed both “redemption date range” and “validity period” to be set simultaneously. Now only one of the two values can be set in a call to the Create Offer API.