What is the difference between program, track, and step levels?
Program level
The Program level is above the Flow. Certain actions can be placed here that looks for qualifying contacts across all tracks with each run.
Track level
Track level refers to the horizontal sections that contain Steps and Decision Points and defines the order of processing. Actions can be placed on the bar above each track, referred to as Apply to a Track, Decision Point action can be placed on the Track, following a Step.
Decision Points that precede Steps are considered placing "on Step" since they are the criteria for the Step.
Step level
Step Level means that actions are placed onto the Step box itself.
Order of execution in actions and steps
Contacts enter a program (via API, database/query or triggered behavior) and the program then processes the actions and their rules in a certain order:
- Lead routes are evaluated at the program level first.
- Move to track actions are evaluated at the program level next.
- Then, actions are evaluated at the track level in the following order:
- Lead routes
- Move to track
- Sync to CRM
- Update profile
- Finally, steps and decisions are followed in the order in which they appear.
- If actions are attached in a step, they are processed in the following order:
- Sync to CRM
- Update profile
- Lead route
- Move to track
- If yes, process the lead routes, then look for move to track.
- If no, then look for move to track.
Note: Display order of actions does not reflect actual execution order.
Can a message send ASAP?
Using triggered events and placing a step at the top of the Start Track creates an Auto-responder like send if no other process tasks exists between entrance and that first step. Applies to first step only. (No programs or track level actions or Decisions before the first Step.)
What happens when a program is activated with unconfigured steps?
All unconfigured items have a red dotted outline around the item.
A program can be activated with unconfigured steps. Activating with unconfigured steps allows incremental development and testing of a program. However, contacts stop and are not processed if they arrive at an unconfigured step (does not skip over unconfigured steps).