How should I use branching logic in workflows?

Last updated: November 1, 2017

Applies to:

Marketing Hub
Professional, Enterprise

Good marketing automation starts with a goal in mind. By using branching logic in workflows, you can further develop distinct nurturing experiences for your contacts based on their behaviors, as a means for achieving the workflow's main goal.

Branching logic allows you to optimize the content you send based on a set of milestones or behaviors, for example, being sent a specific email, clicking a link, visiting pricing page, etc.

You should always enroll a list of segmented contacts in your workflows in order to target a specific type of contact, and use branches to deliver targeted content based on contact's behavior. Avoid enrolling all contacts and using branch logic to do the segmentation.

Let's consider an example of using a workflow to convert marketing qualified leads (MQL) to sales qualified leads (SQL):

  • Your workflows enrolls contacts based on having submitted an MQL form on your website or by being added to an MQL Smart List.
  • Use workflow steps to send nurturing emails to the MQLs
  • You may have a branch that sends the contact a link to talk to sales if they visit your pricing page.

This is a good use of branch logic, since we are enrolling a segmented list of contacts and using branches to send targeting content based on the lead's behavior. Leads that do not visit the pricing page will continue to be nurtured, and those that complete the milestone of visiting the pricing page will receive a targeted email.

Learn how to use branching logic in workflows here.

Was this article helpful?

If you still need help you can get answers from the , or to contact support.