Version September, 2026

Moment templates using different event sources

AVAILABLE ON REQUEST

Background

Interactive Moments help you respond to customer activity as it happens. Until now, Moments listened by default to signals generated directly through the Moments SDK or APIs sending signals.

With this release, you can also choose from additional application sources that are already configured for your account, such as Loyalty or Integrations like Shopify or CDPs. This makes it possible to use customer activity from connected applications, for example a Shopify event, to trigger a Moment without requiring additional technical configuration for that Moment.

This gives marketers more flexibility to create real-time experiences based on customer activity happening across the wider platform.

In-product details

A new App Source field is available under Moment Settings when your account has at least one additional application source configured besides Moments.

The available options depend on the applications configured for your account and can include:

• Moments — Signals generated through the SDK, API server to server connection or Google Tag Manager. This remains the default option.
• Loyalty — Signals generated through the Loyalty application.
• Integrations — Signals coming from configured integrations, such as Shopify. For example, an item added to a cart, a purchase made.

If your account only uses Moments as a source, the App Source field is not displayed and nothing changes in the way you configure or use Moments.

 

Fine-tune Moment targeting with Conditions

AVAILABLE TO ALL CUSTOMERS

Background

Moments already let you respond to customer activity as it happens. With this release, you can make that targeting more precise by adding Conditions directly to a Moment.

Conditions let you define additional rules based on the data contained in the event that triggers the Moment. This makes it possible to target a more specific subset of customers without requiring technical support or additional configuration outside the Moment.

For example, instead of triggering a Cart Abandon Moment for every abandoned cart, you could add a condition so that the Moment is only triggered when the cart value is greater than a specific amount.

This gives marketers more control over when a Moment is raised and helps ensure that real-time interactions are triggered only for the customers and events that matter to a particular use case.

In-product details

A new Conditions section is available for supported Moment types.

The condition builder uses the event associated with the Moment and lets you create expressions based on the attributes available in that event. The Moment is triggered only when the expression evaluates to TRUE.

For example, a Cart Abandon Moment could be limited to carts above a certain value, while a Post Purchase Moment could use purchase details to further refine which customers qualify.

The builder also includes validation and formatting options to make expressions easier to create and manage. Conditions are optional, so existing Moments continue to work as before when no condition is defined.