Triggered personalization
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:
- Trigger - defines the event that starts the personalization, such as a form event or custom event.
- Conditions - optionally control which visitors qualify.
- Action - defines what happens when the trigger occurs and the conditions are met.
For example, an abandoned cart personalization could work like this:
- Your organization sends an abandoned cart event to SitecoreAI.
- The event matches the configured trigger and starts the personalization.
- SitecoreAI checks any configured conditions.
- SitecoreAI uses available profile and event data to personalize the content.
- The configured action sends the resulting data to its destination.
- 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.