Journey Builder Behavioral Trigger

get it to work.

Create ‘Behavioral Trigger’

Journey Builder → click ‘Behavioral Triggers’ → in the top right, click ‘New Trigger’ button → Choose the customer action that is logged in the target data extension when the action occurs, select 1 of 3:

1. Abandoned Cart

2. Abandoned Browse

3. Abandoned Wishlist

→ click ‘Next’. → Set the suppression period and suppression rule: one related to multiple triggers and the second to a recent purchase. For initial configuration, I recommend setting both to 0. It will make testing much more manageable. Once you go to production, change those appropriately as per your business requirements. When you confirm the setup, Marketing Cloud Enagement creates the system Data Extension to store Behavioral Trigger data (one per scenario). → The only option left is the ‘Session Timeout Limit’. You can access it by clicking the ‘gear icon’ button next to the ‘New Trigger’ button. You can select from a range starting at 15 minutes and going in 15 minutes increments up to 3 hours. Again, for testing purposes, make it the shortest possible and later update based on business needs. → Click ‘Next’. → Review and save your settings. The trigger appears on the ‘Behavioral Triggers dashboard’. Note the data extension name so you can select it to power a journey or email send.

Set up a behavioral trigger to map data to a target data extension when a user takes a particular action, such as abandoning a cart or browser session. The target data extension name displays on the ‘Behavioral Triggers dashboard’ after you create the trigger.

Behavioral Triggers Prerequisites

Einstein Recommendations, get a license and enable it in your Business Unit.

Behavioral Triggers Prerequisites

Have Product Catalog, so be sure to configure it before capturing the events.

Behavioral Triggers Prerequisites

Need Einstein Profile (IGO_PROFILE), so you need to enable Einstein Data Extensions.

Behavioral Triggers Prerequisites

Implement the Collect.js script on your e-commerce to capture session and engagement data. This is the ‘Collect Tracking Code’.

Behavioral Triggers Prerequisites

configure Behavioral Triggers to bring relevant data to Marketing Cloud Engagement Data Extensions

Edit a Behavioral Trigger

Journey Builder → click ‘Behavioral Triggers’ → click ‘down arrow button’ next to a trigger. → Click ‘Edit’. → Update the suppression period or suppression rule time frame. → Click ‘Save’.

Pause a Behavioral Trigger

Journey Builder → click ‘Behavioral Triggers’ → click ‘down arrow button’ next to a trigger. → Click ‘Pause’.

The trigger’s status updates.

Resume a Behavioral Trigger

Journey Builder → click ‘Behavioral Triggers’ → click ‘down arrow button’ next to a trigger. → Click ‘Resume’.

The trigger’s status updates.

Set Behavioral Trigger Session Timeout Limit

Journey Builder → click ‘Behavioral Triggers’, in the ‘Behavioral Triggers’ app, click the ‘gear’ button → Select a ‘timeout limit’. → Click ‘Save’.

This timeout limit dictates how long a customer’s session lasts before it’s considered abandoned.

Yes

In order for Behavior Trigger to work, do you need an email with ‘Behavioral Trigger’ block?

Behavioral Trigger ‘Suppression Period’

The [ ] defines a minimum waiting window between repeated triggers for the same individual. It enforces a frequency cap to protect your brand from spamming users who perform multiple abandonment events within a short timeframe.

• How it works: Once a subscriber performs an action that fires the behavioral trigger, they enter a lockout phase for the number of days you specify.

• Example: If you set a suppression period of 7 days, and a customer abandons a cart on Monday, they will be logged into the target data extension. If they return on Wednesday and abandon another cart, the system will suppress (skip) logging that action because they are still within the 7-day lockout window.

Behavioral Trigger ‘Suppression Rule’

The [ ] sets the lookback time frame to evaluate exclusion criteria—most commonly, a customer's recent purchase history. It prevents sending awkward "You left this in your cart!" messages to people who have actually completed a purchase.

• How it works: The rule cross-references your catalog and tracking data to verify if a user has met the conversion criteria within a specified number of days prior to the event.

• Example: If you configure a [ ] looking back 3 days, the trigger will check if the user bought an item in the last 3 days. If they have a successful transaction recorded in that timeframe, the trigger is suppressed, and they will not receive an entry into the abandoned journey.