About the "Jump To" automation action

The "Jump To" automation action is used to measure the effectiveness of your marketing. When used correctly, it can provide a snapshot of how a specific part of your marketing is performing. 

In addition, the "Jump To" action is a way to move a contact to another location within an automation as soon as they meet the specific conditions to do so. These conditions are configured in the "Jump To" action.

Once a contact meets the "Jump To" conditions, they immediately jump from their current location to the "Jump To" action, skipping all steps in between. They will then proceed to the following action in your automation. Once a contact meets the required conditions in a "Jump To," they are considered to have met the "Jump To" action conditions.

Contacts can only encounter a "Jump To" once per entry into the automation. If you want contacts to encounter a "Jump To" action more than once in an automation, they need to exit the automation, then re-enter it. 

Take note

If adding the "Jump To" action to an "Active" automation, make sure to set the automation to "Inactive" first. Once you're done editing the automation, set it back to "Active" so contacts can continue to enter your automation and proceed through your workflow. 

How contacts encounter "Jump To" actions

A contact can encounter a "Jump To" action in two ways:

• Organically
  Contacts can encounter a "Jump To" action if it is the next step in their automation path.
• Jumping
  Contacts can jump directly to a "Jump To" action from their current position in an automation if they meet the conditions set in the "Jump To."

To encounter a "Jump To," the automation must be set to "Active" and a contact must be in the automation containing that "Jump To." 

Anatomy of a "Jump To" action

The "Jump To" action contains five elements. You'll need to provide information or direction for each component to configure it correctly. The five elements are:

1. The "Jump To" name ("Name")
   This is the internal name for your "Jump To" Contacts will not see this name.
2. The "Jump To" condition ("Jump to this action when conditions are met")
   You create a condition that contacts must meet to jump to the "Jump To" action. This condition is created using the segment builder; you can use almost any data in your account to build it.
3. Location ("And when this action is")
   This determines if contacts are eligible to meet the conditions of a "Jump To" based on their current position in an automation. There are two locations to choose from:
   • Below contact's position
     A contact can meet the "Jump To" conditions and move to a "Jump To" action if it is placed below the contact’s current position in the automation.
     
     • When If/Else actions are used, a contact can meet the conditions for a "Jump To" depending on where the "Jump To" is placed:
       • • If a "Jump To" is below an If/Else, and the contact meets the "Jump To" conditions when above the If/Else, they can move to a "Jump To" on either side of the If/Else action.
         • If a contact follows a branch after an If/Else action, they can only meet the conditions for a "Jump To" that is below them in that same branch.
     • If a Go To action is used to connect different automation paths, a "Jump To" may not be considered below the contact’s current position.
     • If the "Jump To" is above the contact in the automation, the contact cannot meet its conditions and will not move to it.
   • Anywhere
     A contact can meet the conditions of the "Jump To" and move to it from any position in the automation. This setting can be used if your automation contains an "If/Else" fork, allowing the contact to jump from one path in your automation to the "Jump To." Note that if a contact (1) encountered a "Jump To" and (2) did not meet its conditions, they will not jump up to the "Jump To" if they meet the conditions later. A contact can only encounter your "Jump To" action once per entry.
4. Action ("If the contact does not meet the conditions")
   You can decide the following action contacts will take when they organically arrive at the "Jump To" action, but do not meet the conditions to move forward. The three actions you can choose from are: 
   • Continue anyway
     Contacts will proceed to the following action in the automation.
   • Wait until the conditions are met
     Contacts will queue in this "Jump To" action until they meet its conditions to proceed to the following action. There is no time limit to how long connections will wait.
   • End this automation
     Contacts will end the automation as soon as they reach this step.
5. Add tracking ("Select a Conversion")
   For contacts who meet "Jump To" conditions, you can trigger a conversion, no conversion, or create a new conversion. Learn more about Conversions. 

How to add a "Jump To" action to an automation

1. Click Automations on the left menu, then click "Edit" for the automation you want to edit.
2. Click the node (+) where you would like to place the "Jump To" action in your automation. 
3. In the “Add an action” modal, click “Workflow” then click "Jump To."
4. The "Jump To" modal will appear. Type the name of the "Jump To" into the "Name" field provided. As a best practice, we recommend choosing a name that describes the desired outcome of the "Jump To."
5. Use the segment builder to set your "Jump To" conditions. 
6. Click the "And when this action is" dropdown and select either "Below contact's position" or "Anywhere."
7. Click the "If the contact does not meet the conditions" dropdown and choose an option. This determines the action contacts will take when encountering this action in your automation, but do not meet the "Jump To" conditions.
8. Optional: Click the checkbox next to "Add tracking" and "Select a Conversion" in the dropdown if you want this "Jump To" to trigger a Conversion. 
9. Click the "Save" button.

Creating segments with "Jump To" data

There are four segmenting options available with the "Jump To" action:

1. "Has jumped to"
   Contact met the conditions of the "Jump To" while going through the automation.
2. "Has not jumped to"
   Contact exited the automation before achieving the "Jump To" or has not yet met the "Jump To" conditions.
3. "Has skipped a jump to"
   Contact reached the "Jump To" action but either skipped it or ended the automation.
4. "Is waiting at a jump to"
   Contact is queued at the "Jump To" action and will only proceed once they have met its conditions.

Note: Contacts who match the "Has skipped a jump to" condition will also match the "Has not jumped to" condition.