Goodbye Template

Overview

The Goodbye use case allows you to target consumers when they unsubscribe from your website, newsletter, game, etc. You can send them a sorry to see you go message or an incentive to remain a member of your community. Also, when people are leaving, it is important to get feedback on the reason why and use this information for future improvements.

To track when an unsubscribe is happening, the cancel event needs to be tracked. This signal, with details on what the visitor is canceling, is then sent to the Moments application. These signals are picked up by the Goodbye Moment.:

 

Configure the Goodbye Moment

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

Settings

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

Moments preferences

Signout

Signout contains the type of signout. You can choose from newsletter, webinar, game, event, website or program. By setting the type, the Moment will only listen to signals of that specific type and ignore the others. This means that you can treat signups differently depending on the type.

For example, when a customer cancels their subscription for your website, you want to send them a sad to see you go message, but when the customer signs out of your webinar, you send them a different message with another possible date to join.

Interest

Interest contains the category of interest. This is a free text field and can be used to specify further details, such as the sports section for the website, or Finance for the newsletter.

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: