We’re launching a new dashboard within the Insights module to report on operational Campaign metrics, enabling you to quickly analyze relevant details and metrics associated with campaign performance. The Campaigns dashboard will serve as a visual toolset for you to gain invaluable insights across past and current campaigns by providing the ability to dive into a specific campaign, or compare KPIs across multiple campaigns of interest. There will be two sub-tabs within the Campaigns dashboard:

1. A deep-dive dashboard view to allow marketers to drill down into engagement and transactional metrics for specific campaigns.
2. A tabular tracker for at-a-glance comparison of high-level KPIs across campaigns.

This new dashboard will be rolled out to each customer's Insights module over the course of May and June. You can preview what to expect with this new dashboard by visiting our SessionM Documentation site.

We've added two new attribute cards to the Composer Builder interface, which is still in Beta release.

Birthday
The card lets you segment an audience based on their birthday. You can segment customers whose birthday is Today, This Month, Next Month, or coming up in a specific number of days, weeks, or months. For example, if you select a birthday coming up in a week, the system will return customers whose birthday is 7 days away.

Customer Lifetime Value
You can segment an audience by their customer lifetime value as measured by either the customer's estimated yearly spend or their estimated spend percentile. Estimated yearly spend covers how much the customer may have spent that given year and can be filtered in several ways (e.g. Equal To, Greater Than, Less Than, Between). Estimated spend percentile covers in which percentile of spending a given customer may fall and can be refined by a Top or Bottom percentile of your choosing.

We've added the Schema Navigator function to the custom SQL Query card in Composer Builder. You can access this feature from the three-dot menu in the top right of the card. This will open a drawer showing the full schema navigator, allowing you to search your schema and easily add content to your card.

Any card that is converted into an SQL query card will have this option available.

We've added the ability to include dynamic point outcomes in messaging to customers. When a customer achieves a campaign outcome in which points are awarded — either a fixed or variable amount (e.g. points per dollar) — this value can now be dynamically referenced within the body of external messaging that is set up as the outcome.

This can be used to create more specific and personalized messaging to the awardee after a point outcome has been achieved.

We've expanded where you can use the Qualifying Context restriction when setting up a behavior for a campaign. This restriction is now available for every Purchase Event. This allows you to evaluate attributes from the business-defined (custom) data object when creating behavior restrictions.

In addition, we've added a new Type option to the Qualifying Context of "Date Time," which will populate the Values field with a date/time picker.

We've added the ability to use open_time rather than modified_time when evaluating transactions for campaign qualification. This is a configuration setting and won't be turned on unless requested. If you are interested in turning on this configuration change, please contact your Customer Success Manager.

Additional campaign catalog data related to a campaign’s goal is now available via the Campaigns API. New values will be returned in the body of the API response, under "behaviors." These values include:

• category_external_ids
• event_data_names
• excluded_category_external_ids
• excluded_event_data_names

Fixed an issue that caused the behavior functionality to break when you created a behavior and then went back and changed it to use the Unit Precision field.

Fixed a UI bug where the Message Information section of a campaign displayed an incorrect status of "Triggered - No trigger specified" for scheduled messages.

We’ve launched a second iteration of the SessionM loyalty connector for Salesforce Service Cloud. SessionM syncs with Service Cloud to provide a customer’s profile information, recent purchase transactions and behaviors, as well as the ability to enroll new customers into a loyalty program and award loyalty points as compensation. The V2 connector brings a simpler interface for configuration of loyalty elements within SFSC and details on installation/upgrade can be found on the Integrations section of the SessionM documentation website.

We've added the ability, via API, to adjust a customer’s date of next tier evaluation. This is useful for “Freezing” a customer’s tier if they cannot participate in the Loyalty program for some time. For example, during the COVID-19 pandemic, if you want to provide your loyalty members with an extension of their current tier, this feature makes that a simple update.

The SessionM Economy Rules module is undergoing an overhaul to create a more streamlined approach to managing tier and rule configurations. The redesigned module is called Loyalty Program and is in beta testing. Please contact your SessionM SessionM Customer Success Manager for additional details on general availability.

When setting up a Point Account, you have the option to allow it to have a negative balance. For example, if a customer returns an item, you can still deduct the points awarded to them even if that means their balance goes into the negative. Previously, we could only deduct points from a point account after the customer first earned points there. With this release, your customers can start spending points (and go negative) before any points are earned by them. This is set on a per point account basis and not across total point balance.

As part of a large body of work to create more flexible loyalty programs, SessionM has created a new Rule Management module (formerly part of the Economy Rules module). The features below are in beta testing. Please contact your SessionM SessionM Customer Success Manager for additional details on general availability. In addition to an improved user interface and experience, the Rule Management module offers the following features:

Ability to Create Rules Based on Business-Defined Data

You can now use the business-defined data (summarized in our September 2020 release notes) to create rules that apply specifically to your business cases. For example, you can work with the SessionM implementation team to define a field of “Start Location of Flight” that enforces a rule that only allows customers flying out of Boston to have 200 points awarded. Due to its flexible nature, this is applicable across industries.

Ability to Create Outcomes Based on Business-Defined Data

The business-defined data allows the SessionM Platform to ingest numeric values where specified, expanding the types of behaviors you can reward. Instead of awarding a customer points based on an amount spent, the customer could be awarded points on a custom field, such as per “Miles Flown.”

Ability to Award Points on Quantity

Similar to the above item, you can award your customers points based on the quantity of a transaction. For example, within the Oil & Gas industry, customers are commonly awarded on liters of gas purchased.

Transaction and Item Status Fields

You can now add a status to either the full transaction or a specific item. This covers use cases such as marking a purchase as "Shipped" and not awarding points for the purchase until it is “Received."

This is an add-on product. Please talk to your SessionM Customer Success Manager if interested in learning more about the use cases for the Stored Value Product.

When a customer activates or reloads a card, the platform now tracks the relevant ID for the store in which this action happened. This is useful for reporting what stores (virtual or brick and mortar) are seeing the most stored value card traffic.