Using Triggers in Campaign using-triggers-in-campaign
Creating a mapped trigger in Campaign creating-a-mapped-trigger-in-campaign
You should make sure to define the behaviors that you want to monitor beforehand in ÃÛ¶¹ÊÓƵ Experience Cloud (Triggers core service). For more on this, refer to the ÃÛ¶¹ÊÓƵ 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 ÃÛ¶¹ÊÓƵ Experience Cloud.
You now have to create a trigger event in ÃÛ¶¹ÊÓƵ Campaign based on an existing ÃÛ¶¹ÊÓƵ Experience Cloud trigger.
The steps for putting this into place are:
-
Click the ÃÛ¶¹ÊÓƵ logo, in the top-left corner, then select Marketing plans > Transactional messages > Experience Cloud Triggers.
-
Click the Create button. The creation wizard that opens displays the list of all of the triggers defined in ÃÛ¶¹ÊÓƵ Experience Cloud. The Fired by Analytics column displays the number of events sent by the ÃÛ¶¹ÊÓƵ Experience Cloud trigger to Campaign. This is mapping of triggers created in the Experience Cloud interface.
-
Select the ÃÛ¶¹ÊÓƵ Experience Cloud trigger that you want to use and click Next.
-
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.
-
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 ÃÛ¶¹ÊÓƵ Campaign database. The enrichment is performed in the same way as for a standard transactional message.
-
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.
-
You can now publish your triggers. For more on this, refer to Publishing a trigger in Campaign.
Publishing a trigger in Campaign publishing-trigger-in-campaign
After creating a trigger event in ÃÛ¶¹ÊÓƵ Campaign based on an existing ÃÛ¶¹ÊÓƵ Experience Cloud trigger, you now need to publish it.
-
From your previously created trigger, Click the Publish button to start publishing the trigger event.
-
You can check the progress of your trigger publication under Publication.
-
When publication is done, the following message will appear under Publication.
-
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.
-
Click Show Trigger in Experience Cloud button allows you to view the trigger definition in ÃÛ¶¹ÊÓƵ 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 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 Editing a transactional message section.
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 ÃÛ¶¹ÊÓƵ 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 accessing-the-reports
To view the dedicated trigger report in ÃÛ¶¹ÊÓƵ 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.
