Conversion Abandon Template

Overview

The Conversion Abandon template allows you to re-engage customers who start a key conversion process but don’t finish, bridging the gap between intent and action to recover lost opportunities.

Examples:
A customer completes the first step of a conversion. If no further progress is detected after X time, the moment is raised.
A customer reaches step two (signals: conversion create / conversion update). If no further progress is detected after X time, the moment is raised.
A customer starts a conversion but then removes their changes. The conversion delete signal resets the timer, and the moment is not raised after X time.
A customer starts a conversion, removes their changes, but then creates another conversion within X time. The moment is raised.

To be able to track the behavior of the visitor and to detect when a specific action has started, stopped or completed, the following events are tracked and sent as signals to the Moments application: Start, Update and Complete. These signals are picked up by the Configuration Abandon Moment.:

Configure the Conversion abandon template

To configure a Conversion Abandon Moment, the following properties need to be set.

Settings

Check out the topic on creating a Moment for details on these generic settings.

Moment preferences

Duration

The Duration is the time delay after which the conversion is considered as abandoned and the Moment is triggered, for example after 2 hours of inactivity on the conversion.

App sources other than Moments to trigger the Moment (optional)

Note: The App source field is only displayed when at least one additional source, besides Moments and Signals, is configured for the environment. For example if you have a Loyalty integration, those events can also be used as a source for Interactive Moments to listen to.

The App source field let's you select additional sources for the Moment to listen to, such as Loyalty or Integrations.

Conditions to filter the signals triggering the Moment (optional)

Conditions let you define a filter on the incoming signals for this specific Moment using any attribute of the selected event.

When no condition is defined, all signals are captured.

Details on how to define a filter are available in the article Expression builder.

Note: The list of events that can be used for filtering corresponds to all the events that are available for this specific Moment and that are listed in the info box at the top: