CRM Ads
- To use the CRM Ads channel, CRM Ads needs to be activated on your account.
- There is a 1-hour delay before the audience is synchronized between Interactions and CRM Ads to make sure that Emarsys is aligned with certain limitations (e.g. according to a Facebook requirement, the audience should contain a minimum of 1000 contacts).
- You can add multiple CRM Ads - add and remove nodes to a program depending on the specific use case (e.g. you would like to remove contacts from the CRM Ads audience after a Wait for a purchase event to reduce the costs of the ad). It is also possible to have a single CRM Ads - add and multiple remove nodes in a program if the CRM Ads - remove nodes use the same asset within the journey.
CRM Ads - add
This node adds contacts who pass through it to the selected CRM Ads audience.
You can select only CRM Ads campaigns if their asset type is Automation Center Audience.
CRM Ads - remove
This node removes contacts who pass through it from the selected CRM Ads audience.
You can select only CRM Ads campaigns if their asset type is Automation Center Audience.
Send email
In the Send email node, you can select an email that will be sent to contacts as soon as they arrive at the node.
Please consider the following when using Send email nodes:
- Interactions uses Triggered Email mail streams to send messages to your contacts.
- Triggered Email ignores the opt-in status of the contacts it sends to. If you would like to send emails to only those contacts whose opt-in status is
TRUE, place a Decision node using the Included in segment template before the Send email node and set it accordingly. - To avoid reducing the efficiency of email deliverability, we recommend adding the Email valid Equal yes contact criteria to your segment used by the Decision node before the Send email node.
- You can only activate your program if the selected Triggered Email mail stream is activated and if its Trigger source is Interactions event.
- You can use the same Triggered Email mail stream in multiple programs or multiple times in the same program.
Mobile Engage push message
You will see this node if you are using the Mobile Engage channel. If you double-click this node, then you can select a push message which will be sent to contacts as soon as they arrive at this node.
You can select only Mobile Engage campaigns using the Automation Center recipient source in this node.
Loyalty trigger
The Loyalty trigger node is only available if the Loyalty Add-on is enabled on your account.
You can create Interactions programs that trigger Loyalty actions with this node.
Why should I be using the Loyalty trigger node in Interactions?
Interactions provides you with the following opportunities:
- You can create sophisticated event filters by using the Trigger attributes and Last time the event happened templates of the Decision or Decision splitter node,
- You can interact with your contacts right away: send them messages without any delay or notify Loyalty about changes to give rewards to your customers quickly.
- It helps you enrich your campaigns with Loyalty incentives to achieve your goals related to the most popular eCommerce and Retail use cases more efficiently:
- Abandoned cart
- Abandoned browse
- Price drop
- Back in stock
Some actions require you to attach the specific action to your contacts. By doing so, the Loyalty system knows whom to reward when the action is completed.
Use cases
- You can trigger Interactions programs with Loyalty external events and react to them with timely delivered campaigns and trigger Loyalty rewards or actions.
- By using the Loyalty trigger node, you can connect contacts to Loyalty actions even without sending them an email, which is essential in the case of opted-out contacts.
- With Interactions, you can create filters using product details for standard Web Extend events. For example, when customers have purchased a product of a high value brand on your website, you can send them a Loyalty promotion about a complimentary item and offer them extra Loyalty rewards.
- You can offer your customers double Loyalty points or other kinds of treatment to incentivize purchases for the most popular use cases such as Abandoned browse, Abandoned cart, Price drop or Back in stock.
In the following example, we have built an Interactions program that:
- Is triggered when contacts view a product page on your website,
- Filters contacts based on their
opt-infields:- Contacts who opted in for receiving marketing materials will receive the Triple points promo campaign.
- Contacts without opt-in will receive the Triple points for the next purchase campaign in their Loyalty wallet.
- Splits the program into 2 paths with the Wait for event node:
- Contacts who make a purchase within 12 days will continue their journey on the Yes path and receive a balance confirmation email about their Loyalty reward.
- Contacts who have not made a purchase will receive a reminder and:
- Continue their journey on the Yes path if they make a purchase within 2 days and receive a balance confirmation email about their Loyalty reward.
- Continue their journey on the No path if they didn’t make a purchase after 2 days and exit the program.
This is how such a program looks like:
FAQ
How can I use Loyalty information (i.e. points or tiers) in Interactions if Loyalty segments are not available?
The payload of Loyalty external events contains all the necessary pieces of information about the Loyalty status of your contacts (for more information on attributes, see Loyalty triggers). By using the Trigger attributes template of the Decision or Decision splitter node, you can create conditions based on the current tier name, previous tier name, points, voucher name, etc.
By using the Event happened and Last time the event happened historical decision templates, you can also combine Loyalty information with other trigger sources, such as Web Extend. For example, you can check the current tier of your contacts with the Last time the event happened template and filter for the loyalty_tier_upgraded or loyalty_tier_downgraded events with the current_tier.name attribute.
You can also use these details to personalize your content.
Please note that Interactions stores these events only for a limited time period (90 days). If no such event happened in the last 3 months, then contacts will either exit the program or continue the journey on the No branch depending on your program’s structure.
Mobile Engage Inbox message
You can send inbox notifications to your mobile application with this node.
Notes:
- To use the Mobile Engage Inbox message node, Mobile Engage needs to be enabled on your account.
- You can only select Inbox campaigns using the Automation Recipient Source that are launched.
- Inbox campaigns that are not yet launched are not displayed in the drop-down.
Update contact list
You can add contacts to or remove them from a contact list by using this node.
A typical use case
The Update contact list node may come in handy when, for example, you would like to save the customers who have downgraded their subscription plans and those who upgraded their plans into different contact lists. Later, you can use these contact lists to send special deals or a survey to the specific target audience. In this case, you can use the Update contact list node as follows:
The following options are available in the Update contact list node:
- Select or create a contact list - You can create a new contact list or select an already existing one. Contacts will be added to or removed from the selected contact list.
-
What to do with contacts arriving at this node?
- Add contacts to the contact list - Contacts will be added to the selected contact list.
- Remove contacts from the contact list - Contacts will be removed from the selected contact list.
Send SMS
You will see this node if you are using the SMS channel. If you double-click this node, you can select an SMS campaign that will be sent to contacts as soon as they arrive at this node.
You can select only SMS campaigns with the Using an Automation Center program recipient source in this node.
Web Channel
Notes:
- To use the Web Channel - add and remove nodes, Web Channel has to be activated on your account.
- To use a Web Channel campaign in Interactions, select the Interactions recipient source.
- You can use multiple Web Channel campaigns in Interactions programs.
Limitations:
- Personalization does not work for Interactions Web Channel campaigns.
- You can only target identified contacts with Web Channel campaigns used in Interactions programs.
- The status of Interactions programs and Web Channel campaigns are handled independently of each other. Therefore, it could happen that you have an active Interactions program with an inactive Web Channel campaign.
- If a contact enters an audience consecutively before it is removed first (i.e. the contact is still at the Wait node), then it can happen that it will be removed prematurely once it reaches the Web Channel - remove node. For example:
- 17.00.01 -
Viewed product pageevent - 17.05.00 -
Viewed product pageevent - In this case, the second event will be added to the audience around 17.05.00 and the first event will be removed from the audience at 17.05.01. So, the second event will be removed from the audience at the same time as the first one.
- 17.00.01 -
- Disabling a Web Channel node is not supported currently. Disabling a Web Channel node does not pause the related Web Channel campaign. To stop Web Channel campaigns from an Interactions program, remove each node from the program itself.
You can react to the behavior of your website visitors by using the Web Channel - add and remove nodes.
Web Channel - add
This node adds contacts passing through it to the selected Web Channel campaign.
After freezing an Interactions program that contains a Web Channel campaign, you need to open the campaign and deactivate it on the Trigger & Scheduling page, otherwise the campaign will be displayed as active on the Web Channel Dashboard.
Only active Web Channel campaigns the start date of which is on the specific day or in the past (i.e. that are already running) are displayed in the drop-down of the Web Channel - add node. You cannot select scheduled Web Channel campaigns because their start date is in the future.
Web Channel - remove
This node removes contacts passing through it from the selected Web Channel campaign.
Mobile in-app
To use the Mobile in-app channel, you need to have the Mobile Engage Android SDK or iOS SDK.
You can react to certain behavioral patterns within your mobile application or share important moments with your customers by using the Mobile in-app channel. To mention a few examples, you can encourage your contacts to sign up for the trial period, congratulate them for their achievements, motivate them to push their limits, provide them with information that is relevant to their progress or ask for their opinion.
- To use a mobile in-app campaign in Interactions, select the Audience recipient source.
- The When should the campaign be triggered? scheduling settings of your in-app campaign determine when the campaign will be shown to your contacts.
- When configuring the frequency settings of your In-app campaign, please consider that these settings can stop an In-app campaign being shown to your contacts even if the campaign is part of an Interactions program.
If your in-app campaign's audience is a segment and a contact within the Interactions program reaches the Mobile in-app - add node, then this contact will be added to the audience even if they were not included in the original segment.
Mobile in-app - add
This node adds contacts who pass through it to the selected in-app campaign.
You can select only in-app messages that are activated and use the Audience recipient source.
Mobile in-app - remove
This node removes contacts who pass through it from the selected in-app campaign.
You can select only in-app messages that are activated and use the Audience recipient source.
Web Push message
You can send Web Push messages to your contact.
Notes:
- To use the Web Push message node, Web Push needs to be enabled on your account.
- You can only select Web Push messages using the Automation Recipient Source that are launched.
- Web Push messages that are not yet launched are not displayed in the drop-down.