+49 69 83008980 service@xqueue.com
Benötigen Sie Hilfe?

Im Maileon Help-Center finden Sie umfassende Dokumentationen zu unserem System.

Beliebte Suchanfragen: Importe | Rest-API | Integrationen | SMS

‚Split by Interests‘ node – Extension of Marketing Automation

Sie sind hier:

1. Introduction

The Split by Interests node allows you to create complex automation paths based on multiple contact preferences (interests). Unlike the Split by Contact Preference Value node, which evaluates only a single preference, this node combines multiple interests using AND/OR logic.

This method enables a more precise customer journey through interest-based branching.

Typical use cases of ‘Split by Interests’ Node:

  • personalized product recommendations
  • newsletter segmentation
  • interest-based campaigns
  • event invitations
  • loyalty programs

Find this node in Campaigns → Automations section (fig. 1).

fig. 1: The ‘Split by Interests’ node is available in the ‘Splits’ category of the Automation Editor menu.

2. General Use Case

Use the Split by Interests node to separate contacts into different automation paths depending on several interests.

The node can create separate paths for contacts who, for example:

  • are interested in product category A AND product category B
  • are interested in product category C OR product category D
  • have explicitly selected or not selected specific interests
  • have preferences with an unset status

After the node is added to the automation, it contains two outputs (fig. 2):

  • Path 1 – the first condition-based path
  • Else – the fallback path for contacts who do not match any configured condition

To rename the Description or the Path, click the pencil icon.

To add further paths, click Add path. To edit a specific path, click the pencil icon or the corresponding button (Path 1, Path 2, …). The number of node outputs in the automation increases automatically with the configured paths.

fig. 2: The primary division of the node: ‘Path 1’ or ‘Else’.

3. Configuring Split Conditions

Each path can contain multiple preference conditions organized in OR-blocks. Before adding a condition, select a preference from the drop-down menu (fig. 3).

fig. 3: Select a preference from the drop-down menu before adding a condition to an OR-block.

When combining conditions (fig. 4):

Conditions within the same OR-block are combined with AND.
OR-blocks within a path are combined with OR.
When configuring a condition, available preference values are:

  • True
  • False
  • Not set

Not set value allows marketers to target contacts who have no value assigned for a specific preference.

fig. 4: Set preference-based conditions using AND/OR logic and target contacts with True/False or ‚Not set‘ values.

Example (fig. 5):

Preference A = true AND Preference B = false
OR
Preference C = true AND Preference D = Not set

After setting the conditions, OR-blocks and values, click Apply.

fig. 5: Once all conditions, OR-blocks and values are set, click ‘Apply’.

Note: A contact takes a path if at least one configured OR-block matches the contact’s preferences.

Maximum limits (per node):

 AND-conditions per OR-block: 10

OR-blocks: 50

4. Path Evaluation Order

Paths are evaluated sequentially from top to bottom (fig. 6). The automation checks:

  1. Path 1
  2. Path 2
  3. Path 3
  4. etc.

The contact is assigned to the first matching path. If none of the configured paths match, the contact continues through the Else path.

fig. 6: Contacts follow the first matching path, or the Else path if no configured conditions match.

4.1. Managing Paths and Conditions

Split by Interests node supports:

  • adding new paths dynamically
  • editing path names
  • adding multiple preference conditions
  • creating OR-blocks that contain multiple AND-conditions
  • reordering paths using drag and drop
4.2. Validation

Before saving the automation, the system checks that all configured rules are complete.

A condition cannot be saved if:

  • no preference is selected
  • no preference value is selected
Inhaltsverzeichnis