How to add filters to your program effectively
To keep your program’s performance at an optimal level, we recommend starting your program with a Decision node that will filter out most of the insignificant events effectively.
Instead of starting your program with a Decision node that filters contacts by their Opt-In status (which condition would be fulfilled by many of them), it is a good idea to define conditions by using specific attribute filters depending on the payload or by specifying a complex Event happened decision.
How to avoid sending the same campaign to a single contact multiple times in an abandoned browse program
A contact can trigger the same Interactions program multiple times and may receive the same campaign more than once. If various events belong to the same contact, then each of them can trigger message sending.
If, for instance, you have different programs triggered by the Web Extend Viewed product page event, then a contact can trigger one or multiple programs by viewing various product pages. In this case, it can easily happen that a contact triggers the same program more than once by browsing multiple product pages. We have collected useful tips that help you prevent your contacts from receiving the same campaign multiple times.
In the following example, we would like to create a program that will only send campaigns to contacts who viewed at least 7 product pages and which contains the following nodes:
- a Decision node that filters contacts who triggered the
Viewed product pageevent at least7times in the last5minutes. - a Wait node that is scheduled to wait as required (in this example, we scheduled it to wait
20minutes ). - a Decision node that targets contacts who did not perform any activity since the trigger event.
- a Participation check node that allows contacts to proceed along the Yes path again after
3days. - a Channel node (in this example, we have used a Mobile Engage push message node).
Example
The following image shows you how the events that belong to a single contact who viewed 9 product pages (i.e. triggered the Viewed product page event 9 times) travel through this program.
- Each time the contact views a product page, the Abandoned browse program will be triggered.
- The first 6
Viewed product pageevents will be filtered out because they do not meet the criteria defined in this node (i.e. triggered at least 7Viewed product pageWeb Extend events in the last 5 minutes). - The 7th, 8th and 9th
Viewed product pageevents will continue their journey. - Add a Wait node to your program and schedule it as required.
- Due to the Since the trigger timeframe option, all previous events (i.e. the 7th and 8th
Viewed product pageevents) will be filtered out, except for the last one. - Only the 9th event will continue its journey, so the contact will receive your campaign only once.
- The Participation check node ensures that contacts can proceed along the Yes path again after 3 days.
Procedure
To create such a program, follow the instructions below:
1. Add a Decision node to your program and set it as follows:
a. Select the Event happened template.
b. Choose the Web Extend event source.
c. Select the Viewed product page event.
d. Set the Number of events condition to more than or exactly 7 time(s).
e. Set the Timeframe to In the last 5 minutes.
The first Decision node will look like this:
2. Add a Wait node to your program and schedule it to wait as required (if you would like to personalize your content with the Predict Email Recommendations widget, then schedule it to wait 90 minutes).
3. Add another Decision node to your program and set it as follows:
a. Select the template Event did not happen.
b. Choose all the available events by clicking Select all from the dropdown.
c. Under Timeframe, select the option Since the trigger.
If you do not configure the last Decision node properly, then your contacts may receive the campaign multiple times as they might trigger several events during their journey. To prevent this, you have to make sure that only the last Viewed product page event triggers message sending.
This Decision node will look like this:
4. Add a Participation check node to your program and configure it as follows:
a. Select the Frequency option If the following time has passed since this contact last proceeded along the Yes path.
b. Set it to 3 days.
5. Add a Channel node to your program and set it as required.
How to edit Triggered Emails in active programs
To edit the content of a Triggered Email stream in an active program, proceed as follows:
- Freeze your program.
- Deactivate the Triggered Email used in your program.
- Modify the content of the mail stream according to your needs.
- Save the mail stream, then activate it.
- Re-activate your program.
How to control message sending and refer to messages used in other Interactions or Automation Center programs
You can select any email, SMS or Push message used in other Interactions or Automation Center programs. To do so, proceed as follows:
- Double-click the Decision node and choose the type Messages not sent.
- Select the Channel you need.
- In the Message(s) dropdown, all emails, SMS or Push messages will be available for selection even if they are used in other Interactions or Automation Center programs.
Tips for using the Interactions editor
We have collected a few useful tips about the Interactions editor. With the new editor:
- You can drag and drop nodes to the canvas:
◦ To insert a node between two others, drag and drop it on the arrow that connects the two nodes.
◦ To connect two nodes, drag and drop the node on the other one.
- You can add the Finish node to the last nodes automatically, so you don’t need to add it to your program manually.
The New Editor is available in the Automation Center. For more information, see Automation Center - New Editor.
