Ctrlk
Blings.ioLogin
For the complete documentation index, see llms.txt. This page is also available as Markdown.

A/B tests

Split Flow Map traffic between variants and compare viewer paths

Use an A/B test node when you want to compare two or more versions of a message, layout, call to action, or sequence. The node assigns viewers to variants according to the traffic percentages you define.

A/B test node on the Flow Map canvas with Control and Discount offer variants
An A/B test node shows each variant and its traffic percentage directly on the canvas.

Set Up an A/B Test

1

Add an A/B Test Node

Place the A/B test node where the split should happen, then connect the previous scene to it.

2

Name the Variants

Give each variant a readable name, such as Short offer, Long offer, or Urgency CTA.

3

Set Traffic Percentages

Assign a traffic percentage to each variant. Use an equal split when you want a balanced test, such as 50% and 50%.

4

Connect Each Variant

Drag each variant output to the scene or lineup that should play for that variant.

To edit an A/B test, select the node and choose Edit from the node menu.

A/B test node selected with a menu showing Edit and Remove actions
Select the A/B test node, then choose **Edit** to change variants and traffic.

The A/B test editor shows every variant, its name, and its traffic percentage. The total percentage should equal 100%.

A/B test editor with Control and Discount offer variants at 50 percent each
A balanced two-variant test uses a 50% and 50% split.

To run a cautious rollout, edit the traffic fields so most viewers stay on the control path and a smaller group receives the new path.

A/B test editor with Control at 70 percent and Discount offer at 30 percent
Example rollout split: 70% of viewers stay on `Control`, and 30% see `Discount offer`.

Use + Add variant when the test needs more than two paths. Use Equal split to rebalance all variants evenly.

A/B test editor showing three variants after Equal split with 34, 33, and 33 percent traffic
After adding a third variant, **Equal split** distributes traffic across all variants.

Choose a Traffic Split

Test goal
Variant A
Variant B
When to use

Balanced message test

50% Short offer

50% Detailed offer

Use when both variants are ready for equal exposure.

Cautious rollout

90% Current flow

10% New flow

Use when validating a new path with limited traffic.

Three-way creative test

34% Control

33% Urgency CTA and 33% Benefit CTA

Use when comparing more than two complete alternatives.

Good A/B tests isolate one meaningful difference. If the scene copy, layout, CTA, and follow-up path all change at once, the result is harder to interpret.

Test Variant Paths

Preview each variant path before publishing. Confirm each variant reaches the intended scenes, uses the right copy or CTA, and ends in a valid viewer path.

Flow Map basicsDashboard and Analytics

Last updated