A/B Split Testing
Two versions of the same cadence, running side by side. Nobody lands on both, and nobody switches sides halfway through, because the side is decided by arithmetic on their own record rather than a coin toss.
Which arm a lead takes, and why it never changes
arm B- Send: case study
- Wait 3 days
- If replied
- Send: short ask
- Wait 5 days
- Exit
Product figures from the platform’s own defaults - not customer averages
How it works.
Nobody's side is a coin toss
The run identifier goes through a small fixed hash and the remainder against the total weight picks the arm. Nothing random is drawn and nothing is stored to remember the choice, so re-running the same step lands the same side every time.
A ninety-ten split is two numbers, not a different step
Each arm carries a weight and the engine cuts the range in proportion to them, so a ninety-ten division is two numbers on the box rather than a different kind of step. A box you drag on arrives at fifty apiece, which is the even split most people want first.
Each side is a full branch in its own right
Whatever hangs off one side is a full branch of the cadence in its own right, with its own sends, pauses and questions. The two sides never have to meet again, and one of them may simply stop.
Which side somebody got is written down, not reconstructed
Before moving on, the box writes down which side it chose against that person's run. So the population either side can be counted from the event record rather than reconstructed from who received what.
One moment in every run.
Every run passes through the same seven. A/B Split Testing is the lit one, and everything either side of it is a different page in this category.
- 01Trigger
the thing that happened first
- 02Enrol
how somebody gets onto it
- 03Wait
the pause, and what governs its length
- 04Branch
the fork, and which side is taken
- 05Act
the mail, the text, the task that goes out
- 06Measure
what counts as it having worked
- 07Exit
how somebody comes off it
The specifics.
7 facts- Arms
- Two in the box you place. The stored format allows more, each with a port name of its own
- How the side is chosen
- A remainder of the hashed run identifier against the weights added together. An arm with no weight written on it counts as one
- Stability
- Deterministic. Nobody changes sides part-way through a cadence
- Weights
- Fifty and fifty on a new box, held on the arms themselves and changed one arm at a time
- Control groups
- A different mechanism. A percentage set on the sequence parks those people before they take any step
- What it will not do
- No significance test, no winner declared, and no promoting the better side afterward
- Not the same as
- This divides an audience by weight. Reacting to what somebody did is Branch Logic
What starts this, and what it starts.
Automation is only ever a middle. These are the things that set it running and the things that run because of it.
More in Automation & Flows
13 capabilitiesSequences, dispositions and outside triggers that act without being asked.
One address per source, sitting outside the login. The same delivery is never counted twice, every exchange is filed, and a new address cuts that source off.
Enroll a lead once and the cadence carries them at their own pace. Nobody loses their place when the platform updates, and nobody is sent one message twice.
Park a lead for minutes or days between steps. The delay you type is a floor rather than an appointment, so the sending hours can push it later, not earlier.
Nobody gets a message at ten past three in the morning. A pause coming due outside the hours you set is pushed forward before the time is ever written down.
One do-not-contact list per workspace, read on enrollment and read again inside the send, so an address added mid-cadence still stops the next message.
Nobody builds the list by hand. New leads enroll themselves as they are created, and the four checks that can refuse one run on every route into a cadence.
The phone, in the middle of a mail cadence. A rep gets a call task with their name on it, and whatever they log at hang-up decides where that lead goes next.
The do-not-call mark, the callback and the task happen because a rep picked the code, not because they remembered. Twenty-six behaviors, twenty codes shipped.
Six things set a CRM rule off: stage change, field update, new record, reassignment, schedule, inactivity. A filter stops it waking for everything that moves.
Send the mail, assign the owner, raise the task, set the field, move the stage, call a webhook. Six actions, none a placeholder, run in the order you set.
The check between a rule firing and an action actually running. Eight comparisons, every one an AND, so a rule covering either of two things gets built twice.
A text step on the same canvas as the mail and the call. It lands in the thread the SMS inbox reads, so the cadence and whoever answers see one conversation.
A key on a versioned path, seen exactly once, held to the same role and profile a person on your floor is, so it never reaches further than they would.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
Automation & Flows
See a/b split testing on your own floor.
Thirty minutes, your numbers and your data. We will set a/b split testing up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included