Behavioral Trigger

What it is & the business problem it solves

Many visitors put products in their cart, start checking out or look at products, and then leave. Behavioral Trigger is a module of Inspire that detects these abandoned moments per customer and sends the abandoned products to CM's customer data platform (CDP or CXP), so you can follow up with a reminder, for example an abandoned-cart email.

There are two modules in the cockpit (the front-end tool where you adjust the business rules of your predictions):

  • Behavioral Trigger — the standard (batch) version, with six trigger types including price-drop reminders.

  • Real-time Behavioral Trigger — a near-real-time version with the three basic trigger types. Enterprise customers can choose near-real-time instead of batch for this module (see Packaging tier).

Behavioral Trigger sends the products the customer abandoned themselves. It does not add recommendations. If you want alternatives or matching products in the reminder, use Event Based Retargeting.

How it works

  1. Read recent behaviour. After every data load into Inspire (by default every 30 minutes), the batch module looks at the customer events of the last 3 days (fixed, not configurable).

  2. Find abandoned products. For each customer and product it checks whether the trigger event (for example add-to-cart) has been cancelled by a later event (see the table below).

  3. Wait until the customer is inactive. A trigger only fires when the customer's most recent trigger event is at least Trigger Event Type Delay Hours old (default 2 hours), measured against the newest event Inspire has received. All of a customer's products are treated as one session.

  4. Do not repeat. Products already sent for this customer within Trigger Event History Days (default 30) are not sent again.

  5. Apply your rules. Excluded products are removed, the optional price-drop check, product-variant de-duplication and ranking are applied.

  6. Deliver. One event per customer with the abandoned products (ordered by rank) is written to your customer data platform: the CDP or the CXP, depending on the delivery destination that was set up for your account. From there, workflows, segments and MMC Email Campaigns can use it.

What counts as "abandoned"

Trigger type

Starts when the customer…

Cancelled for that product when the customer…

Cancelled for all products when the customer…

abandoned cart

adds a product to the cart

removes that product from the cart

starts checkout or makes a purchase

abandoned checkout

starts the checkout

removes that product from the cart

makes a purchase

abandoned browse

views a product detail page

adds that product to the cart

makes a purchase

abandoned category

applies a category filter on a listing page

removes that filter, or views, adds to cart or buys a product of that category after applying it (the trigger is the category, so cancellation also works per category)

— (a purchase in another category does not cancel it)

abandoned cart pricedrop

as abandoned cart, and the price has since dropped

as abandoned cart

as abandoned cart

abandoned checkout pricedrop

as abandoned checkout, and the price has since dropped

as abandoned checkout

as abandoned checkout

"Cancelled" means the cancelling event happened after the trigger event. A purchase a week earlier does not cancel a cart from today.

Price drop: the price when the product was added (or checkout started) is compared with the current price. The product is only sent if the current price is more than Price Drop Percentage lower (default 10%).

Abandoned category: in this module the trigger is the category itself, not a product. The event contains the abandoned category (there are no product IDs). It needs category-filter tracking on your website and a mapping of your filter names to your product categories (see Prerequisites). For a reminder that also shows recommended products from the abandoned category, use Event Based Retargeting with the abandoned category trigger, which is described in full on that page.

Real-time Behavioral Trigger

The real-time version uses the same logic but starts after each incremental data load (a small, frequent load of only the newest events) instead of after the regular load, and reads only the most recent events. It only offers abandoned cart, abandoned browse and abandoned checkout (no price drop, no abandoned category). It has one extra setting, Max Data Age (Hours): if the newest event is older than this, the run stops with an error rather than sending outdated reminders.

How near-real-time works: with the Enterprise package you can choose near-real-time instead of batch: the module then runs after every incremental data load of the Data module (roughly every 15 to 30 minutes, illustrative: depends on the configured schedule) instead of after each regular data load. Prerequisite: incremental loading must be switched on in the Data module; your CM contact enables it for you.

Example use cases

  1. Abandoned-cart email

  • Scenario: a fashion retailer emails customers 2 hours after they left products in their cart.

  • Channel: MMC Email Campaigns, started by a workflow in your customer data platform.

  • Required products: CDP or CXP, Webtracking, Product Feed, MMC Email Campaigns; Inspire Behavioral Trigger (abandoned cart).

  1. Price-drop reminder

  • Scenario: a DIY retailer tells customers that a product they left in their cart is now at least 15% cheaper (illustrative).

  • Channel: email.

  • Required products: as above, trigger type abandoned cart pricedrop, Price Drop Percentage 15; prices in the Product Feed.

  1. Browse abandonment

  • Scenario: a pet-food webshop reminds customers of products they viewed but did not add to the cart, ranked by margin.

  • Channel: email or a customer segment for advertising.

  • Required products: CDP or CXP, Webtracking, Product Feed; trigger type abandoned browse with ranking on a product attribute.

  1. Checkout recovery

  • Scenario: an electronics webshop follows up on customers who started checkout but did not pay.

  • Channel: email or SMS via a workflow.

  • Required products: CDP or CXP, Webtracking (checkout event), purchase data, MMC Email Campaigns or Campaigns; trigger type abandoned checkout.

  1. Category interest

  • Scenario: a furniture webshop sends a "still looking for a sofa?" message to customers who filtered a category page but did not look at any product from it afterwards.

  • Channel: email.

  • Required products: as use case 1, plus category-filter tracking and the filter mapping in the Data module; trigger type abandoned category.

What you can configure

You can configure these settings in the cockpit. Settings marked Expert need expert rights, which CM staff and customer admins can hold; request them via your CM contact person.

Unless stated otherwise, the settings exist in both Behavioral Trigger and Real-time Behavioral Trigger. There is no schedule setting: the module runs after data loads.

Optional rules (item exclusion, user inclusion, ranking, variant grouping, email filtering) each have an "Enable" setting; the rule is only applied when it is switched on.

Note: If a section can be switched on or off, the cockpit shows an on/off switch for it. If a switch you expect is missing, ask your CM contact.

Setting (cockpit name)

What it does

Default

When to change

Who can change

Behavior Trigger Type

Which behaviour to detect. Batch: abandoned cart, abandoned browse, abandoned checkout, abandoned category, abandoned cart pricedrop, abandoned checkout pricedrop. Real-time: abandoned cart, abandoned browse, abandoned checkout.

abandoned cart

Create one module instance per trigger type you need.

Standard

Price Drop Percentage

(Batch, price-drop types only.) Minimum price drop, 1–100%; the price must have dropped by more than this.

10%

Raise it to only notify on substantial discounts.

Standard

Trigger Event Type Delay Hours

Hours of inactivity after the last trigger event before the trigger fires (0–72).

2 hours

Shorter for faster reminders, longer to avoid emailing customers who are still shopping.

Expert

Trigger Event History Days

How long sent triggers are remembered so the same product is not sent again (0–365).

30 days

Shorter if you want repeat reminders.

Expert

Max Data Age (Hours)

(Real-time only.) The run fails if the newest event is older than this (1–72).

12 hours

Only if data arrives with a known longer delay.

Expert

Enable Item Exclusion / Item Exclusion Expression

Products matching the expression never trigger (for example gift cards, out-of-stock items).

Off

To keep products out of reminders.

Standard

Enable User Inclusion / User Inclusion Expression

Only customers matching the expression get triggers (for example a country).

Off

To limit reminders to a target group.

Expert

Enable Ranking On Item Attribute / Rank Item Condition

Orders the products in the event: recent (most recent first) or product-attribute (by a product attribute, optionally descending).

Off

To show the most valuable or newest product first.

Standard

Show each product once (override)

When several variants (sizes, colours) of one product are abandoned, send the product once (the most recently triggered variant).

Taken from the profile's product-variant setting, else Off

Switch on when your feed lists variants separately.

Standard

Product group column

Which attribute identifies the parent product of a variant.

Taken from the profile

Only when variant grouping is on.

Expert

Enable Email Filtering

Only customers with a valid email address get triggers.

Off

Switch on for email-only use cases.

Standard

Delivery Method

batch (deliver) or none (calculate only).

Batch

Set to None to test without sending.

Standard

Batch Method / Event Type ID / CXP Definition ID

Where to deliver: CDP (event type) or CXP (definition). Set up by CM.

CDP

When delivering to CXP.

Expert

Advanced/expert settings (Enable Item Information, List of Item Features, Enable User Information, List of User Features, CPU, Memory)

Extra product or customer fields in the event (by default email and webtracker client ID); computing resources.

Item info Off; user info On; 500m; 4Gi

When the email template needs extra fields.

Expert

Prerequisites & required CM products

Requirement

Why

CDP or CXP

Inspire reads events from your customer data platform and writes the trigger events back to the CDP or the CXP.

Webtracking (CM's website tracker)

Product views, add-to-cart, remove-from-cart and begin-checkout events. For abandoned category also category-filter events.

Purchase data (order lines)

Purchases cancel triggers; without them customers get reminders after buying.

Standard event types

Events must use the standard event types (Purchase, Add to cart, …); a custom event type is ignored. On CDP these are set up by the Retail & Ecommerce adapter, which is included in onboarding (nothing extra to buy or configure). On CXP the adapter does not apply; the standard event definitions come from Templates.

Product Feed

Product details for the email; current prices for price-drop types.

Data module

For abandoned category: switch on filter events and map your filter names to your product categories. For price-drop types: keeps the price history.

MMC Email Campaigns (or another channel)

To send the reminder, usually via a workflow.

Cockpit

To configure the module.

No other Inspire module is required.

Packaging tier

Inspire is part of the MMC packages Pro and Enterprise; it is not included in Basic or Advanced.

  • Behavioral Trigger: available from Pro (so in Pro and Enterprise).

  • Real-time Behavioral Trigger: Enterprise only. Near-real-time variants are included in Enterprise (no add-on): an Enterprise customer can choose to run the module near-real-time instead of batch (see How near-real-time works above).

Data requirements

Technical minimum requirements (what the module needs to work; these are not quality guarantees):

  • Events: at least one trigger event of the chosen type (for example add-to-cart) in the last 3 days (batch; fixed window), as standard event types, with product IDs equal to the Product Feed IDs. If there is none, the run completes and sends nothing. Purchase and cancel events are optional: without them nothing is cancelled, so every trigger fires.

  • Customers: no minimum number of customers or events is enforced.

  • Identified customers: reminders can only be sent to customers the platform can reach, usually because their email address is known (logged in, newsletter click, earlier order). Anonymous visitors are detected but cannot be emailed.

  • Price drop: numeric prices in the Product Feed and a price history kept by the Data module. Products without a usable historic or current price are silently skipped.

  • Abandoned category: category-filter events, a mapping from filter name to product category, and a product category in the Product Feed.

How to check it works

This module has no cockpit statistics (there is no default statistics template for it) and no event viewer. Check it in your customer data platform instead:

  1. In the cockpit, confirm the module instance runs (run history) after the data loads.

  2. Test on your own website: add a product to the cart as an identified customer, leave, and wait for the delay (default 2 hours) plus the next data load.

  3. In the CDP, open your test profile and check for the Behavioral Trigger event (or the profile properties mapped from it) with the expected products. On CXP, check the event of the configured definition.

  4. Check that buying the product, or removing it from the cart, before the delay prevents the event.

Limitations & common pitfalls

  • No recommendations. Only the abandoned products are sent. Use Event Based Retargeting for alternatives or cross-sell.

  • Standard event types only. If your website sends events under a custom event type or uses product IDs that differ from the Product Feed, the trigger never fires.

  • Short window. The batch module looks back 3 days; older abandonments are never picked up.

  • Delay is measured against the newest data. If data stops arriving, triggers stop firing too.

  • Price drop needs price data. Without price history or with non-numeric prices, price-drop types send nothing, without an error.

  • Volume is limited to identified visitors. Expect far fewer reminders than abandoned sessions; the share of visitors with a known email address is the main limit.

  • Cart value may be missing. Cart events from the website do not always carry an order value; if your email shows a cart total, calculate it from price × quantity.

  • No re-send. Within Trigger Event History Days the same product is not sent again to the same customer, even if it is abandoned again.

  • Abandoned category sends the category, not products, and only works with category-filter tracking and a filter-to-category mapping; without them it runs but sends nothing.

  • Real-time does not support price drop or abandoned category, and needs incremental loading switched on in the Data module (see How near-real-time works above).