ABx Test node

This condition allows to branch the paths in a workflow and define the allocation of customer groups to every path. It’s a good way to test the effectiveness of communication through a given channel and to verify content.

The Group stickiness option in this node lets you keep a profile assigned to the same group in situations when the profile re-enters the node. By default, the profile may be assigned to a different group than before. With Group stickiness enabled, the profile is always assigned to the same group as the first time.

The following list outlines the differences in a flow between group stickiness enabled and disabled:

  1. A profile enters a workflow.
  2. A profile arrives at the ABx Test node.
  3. A profile is assigned to the group A.
  4. A profile finishes the workflow.
  5. A profile re-enters the workflow.
  6. A profile arrives at the ABx Test node.
  7. The profile is assigned to a group:
    • Stickiness enabled: Always to group A, same as the first time.
    • Stickiness disabled: Any group, possibly A again.
Important: Enabling the Group stickiness option may result in an uneven distribution of the test group percentages, especially noticeable with a workflow audience of fewer than 1,000 profiles. This behavior is common and expected.

Node configuration


  1. Click the pencil icon on the node.
  2. Click the Add group button. You can add up to 10 groups.
  3. Optionally, you can select the Equal allocation option to evenly distribute customers between the paths.
  4. If you want to always assign the customer to the same test group, enable the Group stickiness option.
  5. Optionally, you can enable Generate a variant assignment event option. Enabling this will generate group assignment events (automation.abTestVariantAssigned) at each profile transition, which may increase costs due to the additional events generated.
  6. Confirm by clicking Apply.

Example of use


Example of ABx Test condition
Use of the ABx Test node
Note: You can have a look at the use case that involves a workflow that includes ABx Test node.

The aim of this workflow is to compare two email templates. Group A receives a standard version of the newsletter, whereas Group B receives an experimental version.

  1. Start the workflow with the Audience trigger node. In the settings of the trigger, define the recipients and select a start date for the workflow.
  2. Add the ABx Test condition. In the settings of the condition, divide the groups. Group A consists of 80% of the whole audience, whereas Group B consists of the remaining 20%.
  3. Add the Send Email action nodes to every path. In the settings of the actions, select the appropriate templates.
  4. When an email is sent, the workflow is completed.
😕

We are sorry to hear that

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

😉

Awesome!

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

Close modal icon Placeholder alt for modal to satisfy link checker