June 2023 Release Notes

DETAILS

No downtime is required for the release.

Customers & Audiences

Added descriptive error messaging in SQL editor in Composer module

Previously, Composer showed a generic "Request failed with status code 500" message for any error that occurred in the raw SQL query editor. With this enhancement, Composer will now show more descriptive error codes and messages to better help troubleshoot failed queries.

---

Bug Fixes for Added descriptive error messaging in SQL editor in Composer module

• Fixed an issue introduced in a prior release related to customer permissions that was causing the point audit log to not appear in the Customers module

---

Campaigns & Content

New options for point calculation for "Points Per" campaigns

Previously, campaigns configured using the “Points Per” behavior with an "X points per X amount spent" outcome would always calculate the amount spent by only looking at the subtotal sum of the items in the basket.

If a behavior additionally specified that specific items were required to achieve the outcome, the point outcome would be calculated based on the amount spent only on the qualifying items. For example, if a campaign was configured to listen for "purchase of any item" in the "denim" category, then award 1 point per 1 dollar spent, the outcome would only be awarded based on items in the transaction that were in the "denim" category and ignore spend on any other items in the basket.

You will now be given the choice between two options when configuring Campaigns using the Points-Per behavior in either of these scenarios.

When "Points Per" and "Any Item" is selected, you will be able to choose between:

• Calculate using Item Amount — current logic and default option going forward
• Calculate using Order Subtotal — calculate based on the aggregate subtotal passed in the header of the transaction

This enhancement provides you more flexibility to choose the point calculation logic that meets the needs of your specific transaction integration.

When "Points Per" and "Specific Items" is selected, you will be able to choose between:

• Calculate from Qualifying Items — current logic and default option going forward
• Calculate from Total Spend — calculate based on the sum of all item subtotals in the basket

This enhancement unlocks a new campaign use case where a promotion can incentivize the purchase of one or more specific items, while awarding the customer for the entire purchase. For example, you can now run a promotion such as: This weekend only, purchase any item from the Denim category and earn double points on your entire order!

---

Improved internal tracking of campaign outcome changes with transaction updates

We've added additional tracking to SessionM's internal logging so that support teams can more easily understand what processing state the campaigns rules engine was using when evaluating a transaction. This will help support team members to investigate changes to point outcomes in complex refund scenarios resulting from returns, exchanges and cancellations.

---

Enhanced reporting traceability of point deductions from refunds, exchanges and cancellations

When a transaction achieves a campaign behavior, but then is later updated to reflect a return, exchange or cancellation, SessionM will deduct points that were originally earned from an item or items that were not included in the final state of the transaction.

The point audit log, which contains a trail of each users point deposits and deductions, will now include the internal SessionM transaction ID in the record that reflects points deducted due to one of these transaction updates. This will help simplify accounting and finance reporting that track outstanding point liability.

---

Bug Fixes for Enhanced reporting traceability of point deductions from refunds, exchanges and cancellations

• Fixed validation on the "Points (Incentives)" input for variable point outcomes to allow for values between 0.1 through 0.9 in the points field, whereas before values less than 1 were not allowed. 0 is still not an allowed value, and the UI will default to 0.1 when it is attempted, whereas previously the behavior would be to default to 1.
• Fixed an issue with "Points Per" and "Specific Items" campaigns using the “Spend Hurdle” restriction where a transaction that earned points but was later voided or updated as a result of a return or exchange would not result in the correct number of points being revoked from the customer profile.
• Fixed an issue introduced in a prior release related to Organization Management where venue tags would not appear in the campaigns drop down selector.

---

Platform Wide

Bug Fixes for Platform Wide

• Fixed an issue introduced in a prior release related to Rails 4 upgrade that was blocking venues from being created
• Fixed an issue with password reset where the validation on email address was too restrictive