Skip to main content
Sitecore Documentation
Personalize logo
Users
Developers
Changelog
  • Powered byPowered by
Introduction to Sitecore Personalize
Managing accounts and system settings
Identifying guests
Introduction to experiments
Introduction to experiences
Decisioning
View dashboards
Developer Center
Connecting to an external system
Using client-side JavaScript
Using server-side JavaScript
  • Sitecore Personalize
  • Introduction to experiences
  • Introduction to triggered experiences in Sitecore Personalize
Edit in Paligo

Introduction to triggered experiences in Sitecore Personalize

Abstract

Introduction to triggered experiences that enable you to present offers and next best actions in real-time (Sitecore Personalize).

A triggered experience lets you create personalized content that includes dynamic data. You can send the content to an Email Service Provider (ESP) for email distribution or to a SMS/Push service provider for distribution as a text message or push notification (popup message on a mobile device).

We recommend you create a triggered experience if your organization is confident that the customer experience will result in the best outcome. For example, if your organization ran an abandoned cart experiment and wants to put the winning variant in production. If you want to statistically test your variant against a control or other variants, we recommend you create a triggered experiment.

You can trigger the experience when there is a change to data or when an event is raised. You can also define the specific conditions that must be met in order to trigger the experience.

The personalized content in the triggered experience is sent as an HTTP GET or POST request against a webhook. A webhook is a connection to a predefined REST endpoint such as an ESP, SMS/Push service provider, or other destination.

Do you have some feedback for us?

If you have suggestions for improving this article,

Privacy policySitecore Trust CenterCopyright © 1999-2023 Sitecore