Actions now supports triggered campaigns for any execution channel you have connected to AgilOne (e.g. Facebook, Email, SFTP…), with an easy-to-use UI. There is now a new campaign playbook called “Triggered Campaign”. It introduces a new step after the “setup”, where you can :

• Pick the type of trigger you want to use (from the list of events we are tracking for your tenant) : examples include (but are not limited to) “emailSend, emailOpen, emailClick, cartUpdated, productBrowsed, directmailSend, smsOpen, etc…”. This will then be used by the UI to populate the Audience step with a filter that selects customers who “performed the event [event type chosen] in the last [see below for timeframe]”
• Pick the frequency at which the campaign should check for new triggers (and therefore be executed) : the frequency can be as frequent as every 4 hours by default (please discuss with your CSM if you would like to leverage higher frequencies). This drives 2 things : the filter that will be prepopulated “performed the event [event type chosen above] in the last [frequency picked in this step]”, and the schedule (“schedule [hourly/daily/etc] every [4h/days]…”).

The rest of the setup is similar to any regular campaign. You will notice that the Audience step has been pre-populated with the event filter described above (and with the relevant values) : feel free to add more filters to create more complex campaigns, or modify that filter as needed. The schedule is also prepopulated, with the same capabilities as before : if you don’t like the schedule, feel free to adapt it to your needs.

We moved the audience rule “Performed an activity with message” under the folder “Event Activity” and renamed it “Performed an event with message” instead for clarity.

In the same spirit, we renamed the filter “Were included in a campaign” to “Were included in an AgilOne campaign” to make it clearer that it is looking at campaigns executed in Actions only (no ESP data is used in this filter).

Actions now supports triggered campaigns for any execution channel you have connected to AgilOne (e.g. Facebook, Email, SFTP…), with an easy-to-use UI. There is now a new campaign playbook called “Triggered Campaign”. It introduces a new step after the “setup”, where you can :

• Pick the type of trigger you want to use (from the list of events we are tracking for your tenant) : examples include (but are not limited to) “emailSend, emailOpen, emailClick, cartUpdated, productBrowsed, directmailSend, smsOpen, etc…”. This will then be used by the UI to populate the Audience step with a filter that selects customers who “performed the event [event type chosen] in the last [see below for timeframe]”
• Pick the frequency at which the campaign should check for new triggers (and therefore be executed) : the frequency can be as frequent as every 4 hours by default (please discuss with your CSM if you would like to leverage higher frequencies). This drives 2 things : the filter that will be prepopulated “performed the event [event type chosen above] in the last [frequency picked in this step]”, and the schedule (“schedule [hourly/daily/etc] every [4h/days]…”).

The rest of the setup is similar to any regular campaign. You will notice that the Audience step has been pre-populated with the event filter described above (and with the relevant values) : feel free to add more filters to create more complex campaigns, or modify that filter as needed. The schedule is also prepopulated, with the same capabilities as before : if you don’t like the schedule, feel free to adapt it to your needs.

We moved the audience rule “Performed an activity with message” under the folder “Event Activity” and renamed it “Performed an event with message” instead for clarity.

In the same spirit, we renamed the filter “Were included in a campaign” to “Were included in an AgilOne campaign” to make it clearer that it is looking at campaigns executed in Actions only (no ESP data is used in this filter).