Split and merge paths split-paths

Use split and merge path nodes to segment people or accounts according to the conditions that you define. Create paths for the audience or accounts list according to conditions, define each path with action and event nodes for the segment, and then combine the paths and continue the journey.

Video {width="30"} Watch the overview video

A Split paths node defines one or more segmented paths based on either account or people filters. A split based on a people filter is automatically closed with a merge paths node so that all people can move forward to the next step without losing their account context.

NOTE
A maximum of 25 paths are supported.

Split paths by accounts split-paths-by-accounts

(Account journeys only)

Split by accounts paths can include both account and people actions and events. These paths can be split further.

How a split path by accounts node works

  • Each path that you add includes an end node with the ability to add nodes to each edge.
  • Split by account nodes can be nested (you can split the path by accounts repeatedly).
  • Evaluation of each path is from top to bottom. If an account matches for the first and second paths, it proceeds along the first path only.
  • Two or more paths can be combined using a merge node.
  • The node supports the definition of an Other accounts path, where you can add actions or events for accounts that do not match one of the defined segments/paths.

Journey node - split paths by account {width="700" modal="regular"}

Account path conditions account-path-filters

Path conditions
Description
Account Attributes

Attributes from the account profile, including:

  • Annual revenue

  • City

  • Country

  • Employee size

  • Industry

  • Name

  • SIC code

  • State

Custom Objects > Has <custom object>
[Beta]{class="badge informative" title="Beta feature"} The account does or does not have relational schema records. It can also be evaluated against any of the selected custom object criteria, as configured in the XDM relational schema. (See Custom data filtering.)
Special filters > Account has matched buying group

The account is matched with one or more buying groups. It can be evaluated against one or more of the following constraints for a matched buying group:

  • Solution Interest

  • Buying Group stage

  • Buying Group status

  • Engagement Score

  • Completeness Score

  • Number of people in buying group role

Add a split path by account node

  1. Navigate to the journey map.

  2. Click the plus ( + ) icon on a path and choose Split paths.

    Add journey node - split paths {width="300" modal="regular"}

  3. In the node properties on the right, choose Accounts for the split.

  4. To define a condition applicable to Path 1, click Apply condition.

    Split path node - add condition {width="500" modal="regular"}

  5. In the conditions editor, add one or more filters to define the split path.

    • Drag and drop filter attributes from the left navigation and complete the match definition.

    • Fine tune your conditions by applying the Filter logic at the top. You choose to match all filters or any filter.

      Split path node - conditions accounts filter logic {width="700" modal="regular"}

    • Click Done.

  6. To add more paths, click Add path and repeat the previous steps to add conditions applicable to this path.

    You can also label each path based on these conditions or use the default labels.

  7. If needed, reorder the paths according to the priority that you want for the split.

    Path filtering is evaluated in top-down order. Each account proceeds along the first path that matches.

    Click the up and down arrows at the top right of each path card to move it higher or lower in the list of paths.

    Split path node - reorder paths {width="500" modal="regular"}

  8. Enable the Other accounts option to define the default path for accounts that are not a match for the defined segments/paths.

    When this option is not enabled, the journey ends for accounts that do not match a defined segment/path within the split.

Buying group filtering for accounts buying-group-filtering-accounts

You can define a path for accounts associated with buying groups and filter the path using buying group criteria. Use the Account has matched buying group filter to define the path segment using a matched buying group. This filter also includes the option to identify accounts based on the number of assigned roles within a matched buying group.

For example, you might want to evaluate buying group readiness based on the depth (number of people) it has in different roles, such as three decision makers and two influencers. In this case, set the condition to target accounts with a minimum of three (3) Decision Makers and two (2) Influencers in a matched buying group:

  1. Click Add filter and choose the Number of people in buying group role filter.

    Add filter for Account has matched buying group and choose Number of people in buying group role {width="700" modal="regular"}

  2. Define the first role parameter.

    • Set the number of people evaluation to at least with a value of 3.
    • Set the role evaluation to is and choose Decision Maker from the list of roles.
  3. Repeat step 1 to add another buying group role parameter.

  4. Define the second role parameter.

    • Set the number of people evaluation to at least with a value of 2.
    • Set the role evaluation to is and choose Influencer from the list of roles.

    Conditions example for role depth in matched buying group for an account {width="700" modal="regular"}

  5. Click Done when you have all conditions defined for the path.

For the identified accounts, you might then want to add an action node in the path to update the status of the buying group or stage, or to send a sales alert email.

Split paths by people

(Account and person journeys)

Split by people paths can include only people actions. These paths cannot be split again and automatically join back.

How a split path by people node works

  • Split by people nodes function within a grouped node split-merge combination. The split paths automatically merge so that all people can move forward to the next step without losing their account context.
  • Split by people nodes cannot be nested (you cannot add a split path for people on a path that is in this grouped node).
  • Evaluation of each path is from top to bottom. If a person matches for the first and second paths, they proceed along the first path only.
  • The node supports the use of account-person relationships, which allows you to filter people based on their role (such as contractor or full-time employee) as defined in the relationship.
  • The node supports the definition of an Other people path, where you can add actions or events for people that do not match one of the defined segments/paths.

Account journey node - split paths by people {width="700" modal="regular"}

People path filters people-path-filters

Filters
Description
Custom Objects > Has <custom object>
[Beta]{class="badge informative" title="Beta feature"} The person does or does not have relational schema records. It can also be evaluated against any of the selected custom object criteria, as configured in the XDM relational schema. (See Custom data filtering)
Event history
Splits people based on experience events that occurred prior to journey entry. Expand the folder to see all event types configured in Admin > XDM event configuration and select one to add as a filter. Constraints include fields from the selected event, a lookback time window measured back from when the person enters the journey, and an optional minimum number of times.
Person attributes

Attributes from the person profile, including:

  • City

  • Country

  • Email address

  • Email invalid

  • Email suspended

  • First name

  • Inferred state region

  • Job title

  • Last name

  • Mobile phone number

  • Person engagement score

  • Phone number

  • Postal code

  • State

Special filters > Member of Buying Group

(Deprecated) The person is or is not a buying group member evaluated against one or more of the following criteria:

  • Solution Interest

  • Buying Group status

  • Completeness Score

  • Engagement Score

  • Is Removed

  • Role

Special filters > Member of List
(Deprecated) The person is or is not a member of one or more Marketo Engage lists.
Special filters > Member of Program
(Deprecated) The person is or is not a member of one or more Marketo Engage programs.

Account-person path conditions

Path conditions
Description
Role in account

The person is or is not assigned a role in the account. Optional constraints:

  • Role name

Add a split path by people node add-a-split-path-by-people-node

NOTE
When you split paths by people, a Close split paths node is automatically inserted to end the split. A split-by-people path allows only Take an action on people nodes.
  1. Navigate to the journey map.

  2. Click the plus ( + ) icon on a path and choose Split paths.

    Add journey node - split paths {width="300" modal="regular"}

  3. In the node properties on the right, choose People for the split.

  4. (Account journeys only) Set the Attributes used for conditions.

    • Choose People attributes only to use conditions related to the person profile.
    • Choose Account-person attributes only to use conditions related to the person’s role membership within an account.
  5. To define a condition applicable to Path 1, click Apply condition.

  6. In the conditions editor, add one or more filters to define the split path.

    • Drag and drop any of the people filters from the left navigation and complete the match definition.

      note
      NOTE
      If you have custom person fields defined in the account audience schema in Experience Platform, these fields are also available to use as person attributes in conditions.
    • Fine tune your conditions by applying the Filter logic at the top. You choose to match all attribute conditions or any condition.

      Split path node - conditions person filter logic {width="700" modal="regular"}

    • Click Done.

  7. To add more paths, click Add path and repeat the previous steps to add conditions applicable to this path.

    You can also label each path based on these conditions or use the default labels.

  8. If needed, reorder the paths according to the priority that you want for the split.

    Path filtering is evaluated in top-down order. Each person proceeds along the first path that matches.

    Click the up and down arrows at the top right of each path card to move it higher or lower in the list of paths.

    Split path node - reorder paths {width="500" modal="regular"}

  9. Enable the Other people option to add a default path for people that are not a match for the defined paths.

    When this option is not enabled, people that do not match a defined segment/path move past the split and proceed to the next step in the journey.

    When you have conditions defined for each path for splitting your audience on the people level, you can add actions that you want to take on people.

Experience event history filtering experience-event-history-filtering

For a split path by people, you can define a path based on experience events that occurred before the person entered the journey. In the conditions editor, expand the Event history folder to see a list of all event types configured by your administrator. Select an event type to add it as a filter condition.

The lookback time window for event history is measured backward from the moment the person enters the journey. For example, a 30-day window evaluates whether the qualifying event occurred within the 30 days prior to journey entry.

You can further refine the filter using constraints specific to the selected event’s fields. The optional Minimum number of times and Date of activity constraints are both evaluated within the defined lookback window. Because event history data is synced from Adobe Experience Platform, there may be a brief delay before a recently occurring event becomes visible to this filter.

NOTE
The events available in the Event history folder are determined by the Experience Events and fields configurations.

Example: To route people who clicked a link in a marketing email before entering the journey, select the email click event from the Event history folder, set the lookback window to cover the relevant time period, and apply any field-level constraints (such as a specific link URL) as needed.

Split path by people condition for event history {width="700" modal="regular"}

Inactivity filtering

For each of the Event history filters, you can enable the Switch to inactivity filter option. This option changes the filter to an evaluation for an absence of that activity type. For example, add the Direct Marketing Email Opened filter to create a path for people who did not open an email. Enable the inactivity option and specify the email.

Split path by people inactivity condition {width="700" modal="regular"}

Membership filtering

Within the Special Filters section, there are multiple filters that you can use to evaluate a person’s membership in a buying group or Marketo Engage list.

For example, if you want to create a path for people who are members of a buying group and are assigned a particular role, add the Special filters > Member of Buying group filter. For the filter, set the membership as true, select a Solution interest that is associated with one or more buying groups, and set the Role that you want to match.

Split path by people condition for buying group membership {width="700" modal="regular"}

You can also include additional buying group membership constraints:

  • Buying group stage
  • Buying group status
  • Completeness score
  • Engagement score
  • Is Removed
TIP
To exclude members who were removed from a buying group, use the Is Removed constraint set to false. You can also explicitly include removed members by setting this constraint to true.

Marketo Engage list and program membership

In Marketo Engage, Smart Campaigns check membership of programs to ensure that leads don’t receive duplicate emails and aren’t members of multiple streams of emails at the same time. In Journey Optimizer B2B, you can check for Marketo Engage list membership as a condition for your split path by people to help eliminate duplication in journey activities.

To use list membership in a split condition, expand Special Filters and drag the Member of List or Member of Program condition into the filter space. Complete the filter definition to evaluate membership in one or more Marketo Engage lists.

Split path by people condition for Marketo Engage list membership {width="700" modal="regular"}

NOTE
Feature deprecation
In the current Journey Optimizer B2B Edition release, filtering based on list or program membership in a Marketo Engage instance is not supported.

Custom data filtering custom-data-filtering

[Beta]{class="badge informative" title="Beta feature"}

You can use relational schemas (model-based classes) to split paths by account or people. The custom objects are defined within relational schemas, and a product administrator can configure relational schema fields in Journey Optimizer B2B Edition. The selected schema fields are available in the condition editor for use in split path by account and split path by people nodes.

For a Split path by account or Split path by people condition, expand Custom Objects. Add the condition and set the value to true or false. Click Add constraint to use the field values for filtering.

Account conditions example for relational schema custom object {width="600" modal="regular"}

Merge paths merge-paths

Add a Merge paths node to combine different split paths by account in your journey.

  1. In a journey map with a split node that has three or more paths, add a combination of actions and events to each path.

  2. Click the plus ( + ) icon for any one of these paths and choose Merge from the displayed options.

    Journey node - merge paths {width="400" modal="regular"}

  3. In the merge paths node properties, select the paths you want to merge.

    Journey node - merge paths {width="600" modal="regular"}

    At this point, the paths are merged so that accounts from the selected paths combine to a single path that can continue to progress through the journey.

  4. If needed, you can unmerge paths by navigating back to the merge paths node properties and clearing the checkbox for any paths that you want to remove.

Overview video overview-video

recommendation-more-help
journey-optimizer-b2b-help-user