Triggered personalization

Important

Feature availability is part of a phased rollout. Your organization may not see this functionality yet. It will become available when your environment is included in the rollout.

Triggered personalization lets you perform personalized action when a specified event occurs.

For example, your organization can send an abandoned cart event to SitecoreAI when a customer leaves items in their cart without completing a purchase. SitecoreAI can use available profile and event data to personalize a reminder and send it to the configured destination.

You can use triggered personalization to send data or content to:

  • an email service provider (ESP) for email
  • an SMS provider for text messages
  • a push notification provider
  • another external system

SitecoreAI sends data to the destination through a webhook, an HTTP endpoint that receives requests from SitecoreAI.

The data sent in the request is called the payload. A payload can contain fixed values and dynamic values from profile or event data, such as a customer's name, email address, or cart value.

How triggered personalization works

A triggered personalization has three parts:

  1. Trigger - defines the event that starts the personalization, such as a form event or custom event.
  2. Conditions - optionally control which visitors qualify.
  3. Action - defines what happens when the trigger occurs and the conditions are met.

For example, an abandoned cart personalization could work like this:

  1. Your organization sends an abandoned cart event to SitecoreAI.
  2. The event matches the configured trigger and starts the personalization.
  3. SitecoreAI checks any configured conditions.
  4. SitecoreAI uses available profile and event data to personalize the content.
  5. The configured action sends the resulting data to its destination.
  6. The destination uses the data to perform an action, such as sending a reminder or updating another system.

For webhook-based actions, SitecoreAI sends the configured payload as an HTTP GET or POST request.

Next step

Get started to create and configure your first triggered personalization.

If you have suggestions for improving this article, let us know!