The use cases described in this section rely on Experience Cloud Visitor ID. It is also possible to implement them with Experience Cloud Declared ID. Hashed and encrypted declared IDs are also supported.
You can send emails/SMS to a profile which does not exist in Campaign by directly decrypting the encrypted email address/mobile number. But in this case, personalization using profile data cannot be used.

Pre-requisites

In order for these use cases to be implemented, you need to have access to the following solutions/core services:

Browse abandonment Trigger

In this use case, we are going to create a simple trigger that will fire every time a client abandons a visit on the website. This example assumes you already have DTM collecting and pushing data to Adobe Analytics and have all your events created.

Creating an Experience Cloud Trigger

For this use case, we need a simple abandonment trigger. The business purpose is to identify visitors who browse our trip booking website, look at the "Deals" page but don't book any trip. Once we identify this audience, we want to reach back to them within a short period of time. In this example, we choose to send the trigger after a period of 10 minutes.

Using the trigger in Adobe Campaign

Now that we've created an Experience Cloud Trigger, let's use it in Adobe Campaign.

In Adobe Campaign, you need to create a Trigger linked to the one you created in the Experience Cloud.

To create the Trigger in Adobe Campaign, click the
Adobe Campaign
logo, in the top left corner, then select
Marketing plans
>
Transactional messages
>
Experience Cloud triggers
.

Publish the Trigger in Adobe Campaign. This process will automatically create a transactional message template.

To dislay the message template, click the
More
button, on the top right, then click
Trigger Transactional Template
.

Personalize its content and sender details.

Publish the message template. The trigger is now live and functional.

Running the scenario

This use case starts with an initial email sent to your audience with Adobe Campaign.

The recipient opens the email.

He clicks on a link that brings him to your website. In this example, the banner brings the recipient to the home page of the trip booking website.

The recipient goes to the "Deals" page but suddenly stops his visit. After a 10-minute period, Adobe Campaign triggers the sending of the transactional message.

At any time, you can check the Experience Cloud logs to see how many times the trigger fired.

You can also display the Adobe Campaign trigger report.

Search abandonment Trigger

In this use case, we are going to create a trigger to reengage with visitors who went on our trip booking website, searched for a destination, found no successful results, and didn't book anything after that. The general process is the same as in the previous use case (see
Browse abandonment Trigger). We will focus here on how to personalize the remarketing email message.

Creating an Experience Cloud Trigger

Follow the steps described in the previous use case to create the Experience Cloud Trigger. See
Creating an Experience Cloud Trigger. The main difference is the trigger definition.

The
Include Meta Data
section allows you to pass any data collected from Analytics to the Trigger payload. In this example, we create a custom eVar (for example, eVar 3) to collect the search term the visitor enters. This term will then be used in the transactional email message sent to the same visitor.

Using the trigger in Adobe Campaign

Follow the steps described in the previous use case to create the trigger in Adobe Campaign. See
Using the trigger in Adobe Campaign. The main difference is how we access and use, in Adobe Campaign, the meta data pushed in the Trigger payload.

In the Search Abandonment trigger you created in Adobe Campaign, click on the
Event content and enrichment
icon to view the payload pushed to Adobe Campaign.

As you can see, the custom eVar is passed in the Trigger payload and mapped to the Event Context table (ctx). We can now access it to personalize the transactional message.

In this example, we choose to include the destination search term in the subject line as well as in the email body.

When selecting a personalized field, look for your payload meta data in the Transactional event (rtEvent) table then in the Event context (ctx) sub table.

Running the scenario

The visitor goes on the trip booking website and searches for a destination. In this example, the visitor is looking for a trip to Japan but finds no result. This is an opportunity for us to reach back to this visitor and recommend an alternative travel plan.

Note:

In this use case, we assume the visitor/recipient has already opened and clicked on an email originating from the same website. This allows us to use and collect the VisitorID and map it to the recipient. We only need to do this once.

A few moments later, the same visitor/recipient receives a remarketing message. The message includes the recently searched destination.

Twitter™ and Facebook posts are not covered under the terms of Creative Commons.