Show Menu

Using Triggers in Campaign

Creating a mapped trigger in Campaign

You should make sure to define the behaviors that you want to monitor beforehand in Adobe Experience Cloud (
core service). For more on this, refer to the Adobe Experience Cloud documentation . Note that when you define the trigger, you need to enable the aliases. For each behavior (browsing/form abandonment, adding/deleting products, session expired, etc.), a new trigger must be added in Adobe Experience Cloud.
You now have to create a trigger event in Adobe Campaign based on an existing Adobe Experience Cloud trigger.
You can watch this video to help you understand how triggers are set up in Adobe Campaign.
The steps for putting this into place are:
  1. Click the
    Adobe Campaign
    logo, in the top left corner, then select
    Marketing plans
    Transactional messages
    Experience Cloud Triggers
  2. Click the
    button. The creation wizard that opens displays the list of all of the triggers defined in Adobe Experience Cloud. The
    Fired by Analytics
    column displays the number of events sent by the Adobe Experience Cloud trigger to Campaign. This is mapping of triggers created in the Experience Cloud interface.
  3. Select the Adobe Experience Cloud trigger that you want to use and click
  4. Configure the general properties of the trigger. At this step of the wizard, also specify the channel and the targeting dimension to use for the trigger (see targeting dimensions and resources ). Then confirm the trigger creation.
  5. Click the button to the right of the
    Event content and enrichment
    field to view the content of the payload. This screen also allows you to enrich the event data with profile data stored in the Adobe Campaign database. The enrichment is performed in the same way as for a standard transactional message.
  6. In the
    Transactional message validity duration
    field, define the duration for which the message will stay valid after the event is sent by Analytics. If a duration of 2 days is defined, the message will no longer be sent after that duration has passed. If you put several messages on hold, this ensures that those messages will not be sent if you resume them after a certain period of time.
  7. If a propensity scoring is defined in Analytics (see the Experience Cloud documentation ), you can choose not to send the message if the customer has a high probability of coming back to the website in the near future. The content of the score and the threshold is available in the content of the payload so that you can use those values to personalize the message. To use this option, check the box at the bottom of the screen. The clients with a strong probability of coming back to the site in the near future will not receive a message.
  8. Click the
    button to start publishing the trigger event.
  9. If you need to make a change in your trigger schema even after publishing your trigger event, click the
    Update schema
    button to retrieve the latest changes.
    Please note that this action will unpublish your trigger and transactional message, you will be required to republish them afterwards.
Show Trigger in Experience Cloud
button allows you to view the trigger definition in Adobe Experience Cloud.
Once the event has been published, a transactional template linked to the new event is then automatically created. You then have to modify and publish the template that was just created. For more on this, refer to the Editing the template section.

Editing the transactional message template

Once you have created and published the trigger event, the corresponding transactional template is created automatically. For more on this, refer to the Creating a mapped trigger in Campaign section.
In order for the event to trigger sending a transactional message, you have to personalize the template, then test it and publish it. These steps are the same as for a standard transactional message. For more on this, refer to the Transactional template section.
If you unpublish the template, it will automatically unpublish the trigger event.
When editing content, you can add a personalization field based on the information sent by the Analytics trigger. If you enrich the event data with Adobe Campaign profile data, you can personalize the message based on this information. To personalize your message, select
Transactional event
Event context
and select a field.

Accessing the reports

To view the dedicated trigger report in Adobe Campaign, open the trigger event that you previously created, and click
Show trigger report
The report shows the number of processed events compared to the number of events sent by Analytics. It also displays a list of all the recent triggers.