NAV Navbar

ExpandCollapse All


Ability to Duplicate an Audience

You can now duplicate an existing audience to make it easier to create multiple audiences with similar properties. Active or Draft audiences can be duplicated. Simply click on the three dots in the far right column for a particular audience. You’ll be able to rename the audience, and then it will be created in draft mode. Your duplicated audience will appear at the top of the All Audiences main page. Edit the audience properties as needed and then activate the audience when it’s ready.

Audience Targeting by Zip Code Improvement

When building an audience and targeting by Zip Code, you can now paste into the field a comma-separated list of zip codes with no spaces between the entries and no line breaks. There is, however, a limit of 25 for the number of zip codes you can enter in order to retain query efficiency and avoid failures during audience generation. If you need to target more than 25 zip codes, you will have to make multiple audiences to achieve this. The team is looking at future upgrades to ease this restriction.


Campaigns API Enhancement

We’ve enhanced the Campaigns API to now return an external_behavior_id within the Behaviors object, allowing for more granular information. You can read about this new attribute in the Core API docs

Platform Integrations

Listrak Messaging Plugin

We've integrated the Listrak Messaging Plugin via the SMP Campaigns module. The plugin is currently configured to work only with the Triggered delivery method, where a behavior rule is created to trigger the sending of the email. As with all messaging plugins, you need to select the External Message type in your campaign to set this up. You will be able to select the email template to use and can specify a template variant if you want. Messaging template variables (api tags) can be used to populate message templates in Listrak.

New Feature Guardrail: Scheduled emails will be handled via a nightly batch (an Audience Export to a CSV file) from SessionM to Listrak. This nightly batch can be used to update Listrak profiles with SessionM information.

There is no UI interface in the SMP for this plugin. Contact your Customer Success representative if you would like this plugin added to your instance of the platform.

Updated Handlebar Helpers to be Consistent Across Audience Export and Messaging

We’ve updated the Handlebar Helpers that are available for use in Audience Export and Messaging so that the same set is available in both products. Previously, there was a discrepancy between which helpers were available in each product.

Point Economy

Enhancement to the Point Audit Log

This enhancement will allow a user to view the SessionM transaction ID after a "Point Expiration" event in the point audit log for points originally tied to a transaction. This will be helpful in tracking points from a transaction as the points expire or roll over from an escrow account. This will only be relevant to Connect-related point issuances.

Composer (Beta)

Ability to View Export History Details

On the Exports Tab you now have the ability to see the status and details of each export. Click on the three dots in the last column and choose “View History” to reveal a drawer with the export history. You can see the exact time the export started, the file name exported and if the job was completed or not.

Improved Query Building Help Section

he Query Help section on the query building page now has more detailed and specific information related to Audience building and Exports.

Additionally, in an effort to help users understand the values that can be used in the Query builder, we’ve added a link to a PDF of the Data Cloud Schema, which includes all SQL tables and their columns. A future release will surface this information directly in the interface.

Additional Changes


  • We’ve changed the daily export schedule to 2:00 UTC in order to accommodate when the data lake gets refreshed.


  • Now when a client is activated on Composer, we have a fully automated verification process that runs to check the entire workflow, from logging in, creating an audience in Composer, creating an export of the audience and verifying that the audience and the export are showing up in both the Composer and Audience modules.
  • We’ve improved our error monitoring and reporting and now post errors to a Slack channel to ensure maximum visibility.


  • We’ve added triggers to clean up audience tags when they either expire or are manually deleted.


  • In an effort to make Composer much easier to use, we’ve simplified audience queries to now accept user_id in addition to external_id. This change has been added to the Query Help section, as noted above.


Bug Fixes

Reward Store
The get_reward_store_offer request has a field to limit_to_only_active offers, which was incorrectly only evaluating the offer Start and End Dates and not considering the offer status. Now, only an offer that falls within the Start and End dates and is set to Active will be returned to the store.