About Adobe Experience Cloud Triggers about-adobe-experience-cloud-triggers

Integration between the Experience Cloud Activation core service Triggers and Adobe Campaign allows you to send personalized emails to your customers as a reaction to specific behaviors that are tracked on your website by Adobe Analytics (within 15 minutes).

In Adobe Experience Cloud, you define the different triggers, that is to say, the customer behaviors that you would like to monitor, such as all of the clients who abandoned their visit on your website, made a search on your website, but didn’t make a purchase, or even the clients whose session expired. When creating a trigger, you define the trigger’s condition and the data that will be sent in the event (pload) to Adobe Campaign.

In Adobe Campaign, you select the trigger that was previously created, you enrich the event data with datamart data and you define a transactional message template linked to that trigger. For example, when a client abandons their visit on your website, an event is sent to Adobe Campaign which can then leverage this event via a remarketing email that is sent to the client within 15 minutes.

The following diagram details how this integration works.

Related topics:

Triggers user process triggers-user-process

Before executing the main user steps, the functionality needs to be configured. For more on this refer to Activating the functionality, Configuring solutions and services and Creating a mapped trigger in Campaign.

The main steps of the user process, in Adobe Campaign, are:

  1. Create a trigger event linked to an existing Adobe Experience Cloud trigger.
  2. Publish the trigger event.
  3. Define the content of the transactional message template.
  4. Test the template (create a test profile and send a proof).
  5. Publish the transactional message template.

Complete use cases are described in this section.

Important notes important-notes

Here are some important notes to take into account before using the Triggers - Campaign integration:

  • Push notifications are not supported for triggers. Only Email and SMS are supported.
  • You can enrich the trigger with meta data captured through Analytics such as email ID, page name, etc.
  • You can reconcile the trigger to a profile stored in Campaign Standard and use the profile’s fields to personalize the message.
  • As soon a trigger is received, it is processed and reconciled and sent out. It takes about 5 to 15 minutes depending on the volume of triggers received, the number of personalization fields used in template.
For more on best practices and technical limitations, refer to Triggers best practices and limitations.