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.
• A form can be used by only one active (launched) program at a time. If the form is already in use by another active program, it will not be available for selection.
• Programs that start with this entry point follow the ignore 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 all standard system and custom fields here.
• You cannot select certain fields whose values are filled in dynamically, such as ‘Date of first registration’, or ‘Age’.
• Field values can be changed in many ways, for example through data import, API call, form submission, manual change, and so on.

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.
• It has no effect on new contacts entering other programs via other nodes, for example from a registration form or data change.

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).

• If you include external data in the external event API call, this external data will remain available for that contact throughout their journey through the program and can be used to personalize further emails.
• Programs that start with this entry point follow the ignore opt-in rules for transactional programs.

This node allows the contacts of an auto import to enter the program as soon as the import completes.

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. 

Here you can combine a Target segment and an Email node.

• When the program becomes active, the segment will refresh and the email will be launched.

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.

A combination of Recurring schedule, Target segment and Email, which means that at the defined time your selected segment is refreshed and the email is launched.

For more information please see the Send email and Filter sections below.

A combination of a Target segment and a 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.).

This node is used in conjunction with the Transfer participants to another program toggle in the Finish node, 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. You cannot connect any other nodes to the Entry from another program node, you can only connect nodes to the special Wait node following the entry node.
• 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.

In this node you select an email which will be sent to contacts as soon as they arrive at the node.

• 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.

If you are using the SMS channel, you will also see this node. In it you can select an SMS message which will be sent to contacts as soon as they arrive at the node.

If you are using the Mobile Engage channel, you will also see this node. In it you can select a push message which will be sent to contacts as soon as they arrive at the node.

If you are using the Offline Mail channel, you will also see this node. In it you can select a direct mail (print) campaign which will be sent to contacts as soon as they arrive at the node.

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.

Click here for some examples of when to use this node.

If you are using Web Channel, you will also see this node. It adds contacts who pass through it to the selected Web Channel campaign.

If you are using Web Channel, you will also see this node. It removes contacts who pass through it from the selected Web Channel campaign.

If you are using CRM Ads, you will also see this node. It adds contacts who pass through it to the selected CRM Ads audience.

If you are using CRM Ads, you will also see this node. It removes contacts who pass through it from the selected CRM Ads audience.

This node combines Wait node 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.

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.

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.

Here you specify a fixed time and date in the future when the next step is run in the program. Contacts reaching this node are queued until that point.

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 use filters together by either having them on parallel paths (which in effect links them with the OR operator) or in sequence along the same path (in which case they are in effect linked with the AND operator). In each case you should bear the following in mind:

• Parallel filters mean that contacts can progress along two paths if the filters have been so configured. It is up to you to ensure that this does not happen.
• Sequential filters can incur performance penalties if you have a large contact database, and should be avoided where possible. Instead, combine all the criteria together in one filter, or combine multiple filters together in. See: Before you start building programs - Filters. 

Whereas the Segment node only allows contacts in the selected segment to proceed, this discards any contacts in the segment. In this way you can ensure that contacts do not receive the same email twice, 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.

This badge is added to Wait nodes when the program is in Test mode, when test contacts have arrived at the node and have been queued. You can click it to process all the queued contacts immediately.