Here you have a list of all the workspace nodes available, along with a breakdown on what they do and how they work. For practical examples of how they can be put to use, please see the Blueprints section which contains examples of program blueprints.
Transactional entry points
This node allows your contacts to enter the program once they complete and submit the selected form. Only general registration forms can be selected and used here, and forms already in use by another program will not be available for selection.
Programs that start with this entry point follow the opt-in rules for transactional programs.
Here you can select an action based on a change to a specific data field (such as email address). When a contact triggers a change to that field, it causes them to enter the program. You can select system and custom fields here, with the only exception that certain fields which are filled in only once, such as ‘Date of First Registration’, or dynamic fields like ‘Age’, cannot be used. Field values can be changed in many ways through data import, API call, manual change, and so on.
If a form is submitted containing field values that already exist, these will not be overwritten and the program will not be triggered. Only a change in the field value triggers the program, regardless of how it is changed.
This will add all new contacts in the account database to the program, regardless of how they were registered.
This node can only be used in one active program at any one time. However, it will not prevent new contacts from also entering other programs via other nodes, for example from a registration form.
Here contacts can enter a program if they are returned by an API call containing the same external event (you must first create the API call before you can use this node).
Programs that start with this entry point follow the opt-in rules for transactional programs.
If you include external data in the external event AP call, this external data will remain available for that contact throughout their journey through the program and can be used to personalize further emails.
Entry from another program
This node is used in conjunction with End plus add to program, and the two in combination allow you to automate the transition of contacts from one program directly into another. This entry node starts a recurring program that runs once a day. It comes with a built-in Wait node that cannot be removed. In the Wait node you can select only the time of day that the program should run. It behaves like any other recurring program; that is, child campaigns are created for all the emails within it every time it is run.
Clicking this node will show a summary of all the programs connected to that program. New connections cannot be added or removed here, only via their respective Finish and Transfer nodes.
Batch entry points
In this node you select a target segment to enter the program, which can be used as a starting point for an ad hoc batch program that goes through further actions before sending the email. When the program is activated, the segment will refresh and all the relevant contacts then proceed to the next step in the process.
Please note that you can only choose an existing Emarsys or Smart Insight segment here.
Here you can combine a Target Segment and an Email. When the program becomes active, the segment will refresh and the email will be launched.
This node allows the result of an auto import to trigger the next stage in a program as soon as the import completes.
Recurring entry points
This node combines a recurring schedule and a filter. At the scheduled time, the filter will run and all contacts returned will enter the program. For more information on segmentation please see the Filter section below.
The shortest interval allowed is once per day; if you need a more frequent schedule than this, please contact Emarsys Support.
A combination of a Target Segment and a Quick filter. The filter displays all the date fields in your database along with the corresponding criteria (for example 'Is in the future', 'Is today', 'Is in the past', etc.).
Channel message nodes
In this node you select an email which will then launch according to the preceding nodes and program schedule. The email itself can be previewed or edited through opening the properties pop-up. If you open an email from a program, the program name is displayed at the top and you can return to the program via the linked program name at the top.
Emails which are not of the type ‘On program event’ are also available for selection, but they will lose their recipient source and scheduling page once selected.
This triggers an SMS message to be sent whenever a contact reaches this node.
This is only available to SMS Campaign users.
Mobile Engage push message
It sends the selected push message for the chosen recipient source.
Channel distribution nodes
Save contact list
This node collects contacts which pass through it into a contact list. You can specify the name of the contact list, and it will be created when you save the program. When the Add new contacts to existing list checkbox is checked, all the contacts that pass through the node are added to the same list. This is the default setting. If you uncheck this checkbox, the list is overwritten with every new entry. It only makes sense to uncheck it for programs starting with a recurring entry point, since this pushes a batch of contacts through at once. Otherwise only single contacts pass through (and the contact list will therefore only contain the most recent contact). Click here for some examples of when to use this node.
Didn't respond to email
This node combines Wait and a behavior filter. If no response to the email has been identified (for example by clicking a link or downloading images) after the defined time period, the contacts progress to the next stage. The behavior filter automatically references the email previous to it.
Didn't click link
This node combines Wait and a behavior filter. If a contact still has not clicked a link in the email after the defined time period, they progress to the next stage. When you use this node you need to choose from a list of links, which are taken from the email preceding this node.
Only trackable links and landing pages are shown. Add-ons and forms are currently not available for selection.
Time action nodes
Here you specify the delay in hours or days before the next step is taken in the program. You can also specify to wait until a specific day of the week.
All delays specified in days are counted as calendar days, not 24-hour units. If you specify ‘wait 1 day and send at 07:00’ the node will collect content that occurs between 00:00 and 23:59:59, which is then sent out at 07:00 the following day.
Here you specify a fixed time and date in the future when the next step is run in the program.
Filter action nodes
Here you select from simple or combined segments which can be used as simple logic switches that allow you to split paths according to contact properties or responses. In order to use this node you have to have an existing Emarsys or Smart Insight segment that you can apply it to. You can link filters by either having them in parallel (OR function) or in sequence (AND function). Parallel filters mean that contacts can progress along two paths if the filters have been so configured. Sequential filters mean that only contacts have to meet the requirement of each filter to progress. If at any point in the sequence they do not fulfil the criteria, they exit the program.
All contacts who are returned by the segment go to the next step of the program, those who are not are assumed to have exited the program.
Whereas the Segment node only allows contact in the selected segment to proceed, this discards any contacts in the segment. In this way you can ensure that contacts have not already received an email which appears later in the program, for example.
Whereas the Segment node requires you to select an existing Emarsys or Smart insight segment, the Quick filter lets you choose a field and a value on the fly. This is a useful and time-saving way to fine-tune your program.
This node lets you add a segment to the path, which allows contacts to proceed if they are in the segment, and excludes them if not. This lets you filter out contacts using criteria which are not necessarily related to any other segments in the program.
Here you can split the program into different paths, with contacts randomly assigned to each path according to a % value that you set. You can add paths and change the % value while the program is active. However, you cannot delete a path once a contact has entered it. To stop further contacts entering a path, simply reduce the % value to 0.
This is how you end your program, and all paths in a program require this as the final node. This node signifies that all contacts who reach it have exited the program.
Finish and transfer
This is an alternative function of the "End" node, which can be configured to forward participants to the entrance node of a different program. This function can be added to any program, there are no usage restrictions.
This is not a node in itself, but an icon added to a program node when participation settings are applied. You can click on it to open the participation settings menu and change the settings using this icon.