Percentage Split vs Wait for Trigger: Which Rule Fits Each Flow Step

Every automation flow needs rules that decide how contacts move.

Two of the most commonly confused are the percentage split and the wait for trigger.

They look similar on a flow map, but they answer completely different questions.

A percentage split decides which path a contact takes.

A wait for trigger decides when a contact is allowed to keep moving.

Choosing the wrong one does not just make your flow map messy.

It changes what your contacts experience, what you can measure, and how quickly you can fix a mistake.

This article walks through what each rule does, when to use it, and how to decide at each step of a flow.

What a percentage split rule does

A percentage split rule divides contacts between two separate flow paths.

In Mailchimp, the split is random: when a contact reaches the rule, the system assigns them to path A or path B based on the percentages you set (Mailchimp).

You control the ratio with a slider, and the split happens at the moment the contact arrives at that step.

The documented use cases are experiments.

Mailchimp suggests using a percentage split as an A/B test, for example comparing a free-shipping offer against a discount offer.

Other documented examples include testing subject lines, email designs, or timing (Mailchimp).

For timing, one path gets an email immediately while the other receives it after a delay.

Two practical details matter for operators.

First, in Mailchimp this rule requires a Standard plan or higher (Mailchimp).

Second, the split is not permanent: if one path clearly performs better over time, you can edit the percentages to send all future contacts down the preferred path (Mailchimp).

Existing contacts are not described as rerouted, so plan as if they stay on their assigned path.

What a wait for trigger rule does

A wait for trigger rule pauses contacts in place until they meet a condition you have set.

The condition can be based on purchase data, tags, campaign activity, or other segmentation options (Mailchimp).

Until the condition is met, the contact simply sits at that step.

Nothing sends, nothing branches.

The classic example is holding contacts until a tag is added to their profile (Mailchimp).

In a revenue-operations context, that might mean waiting until a contact has opened a key email, completed a purchase, or been marked by sales before the next message goes out.

Mailchimp documents one hard limit: an automation flow can include up to 10 wait for trigger rules (Mailchimp).

That cap is rarely a problem in a simple flow, but in a long nurture sequence with several hold points it is worth counting before you build.

How wait for trigger differs from a time delay

Because the query often comes up alongside time delays, it helps to separate all three rules.

A time delay prevents a contact from continuing for a fixed period you choose, such as adding space between two emails so contacts have time to engage (Mailchimp).

A wait for trigger holds a contact for an unknown length of time, until a condition is true.

A percentage split does neither: it routes contacts immediately down one of two paths.

A useful shorthand:

• Time delay: wait a set amount of time, then continue.
• Wait for trigger: wait until something happens, then continue.
• Percentage split: do not wait at all; choose a path at random.

If you know exactly how long to pause, use a time delay.

If the pause depends on the contact’s behavior or data, use a wait for trigger.

If you are comparing two experiences, use a percentage split.

When to choose a percentage split

Reach for a percentage split when the question is which version works better, not who is ready.

The decision signal is that you have two candidate treatments and no data yet on which performs better.

Typical situations include:

• Testing two offers in the same email position, such as free shipping versus a discount.
• Testing subject lines or email designs against each other (Mailchimp).
• Testing timing itself, by sending one path immediately and the other after a delay (Mailchimp).

The tradeoff is that a split deliberately gives some contacts a worse experience, at least for the duration of the test.

That is acceptable when the difference is small and the learning is valuable.

It is not acceptable when one path carries a real risk, such as an untested offer or a message that could confuse customers.

In those cases, pilot manually or split very conservatively before committing a large share of traffic.

Also plan the end of the test before you start.

Because you can shift percentages toward the winning path once results are clear (Mailchimp), decide in advance what evidence will count as “clear.”

Without that decision, split tests tend to run indefinitely and nobody acts on them.

When to choose a wait for trigger

Reach for a wait for trigger when the next step should only happen after a specific condition is true.

The decision signal is dependency, not comparison.

Common situations include:

• Holding a contact until a tag is added, for example when sales has qualified them (Mailchimp).
• Waiting for purchase data before sending a post-purchase or upsell message.
• Pausing until campaign activity, such as engagement with a key email, has occurred.

The tradeoff is that a wait for trigger has no natural end.

If the condition is never met, the contact waits indefinitely.

That can be exactly what you want for a gated step, but it can also silently strand contacts who will never meet the condition.

Before activating the flow, ask what happens to a contact who never triggers the wait.

Some teams pair the wait with a later cleanup step or accept that those contacts simply stop receiving the sequence.

Another tradeoff is measurement.

A wait for trigger changes each contact’s pace individually, so two contacts entering the flow on the same day may reach the next email weeks apart.

That is usually the point, but it makes time-based reporting on downstream steps harder to read.

Deciding rule by rule in a real flow

Most flows need both rules at different points.

Here is how the decision looks step by step.

At the top of the flow

Early steps are usually about pacing, not testing.

A welcome sequence typically uses time delays to space messages (Mailchimp).

A percentage split here only makes sense if you are genuinely testing two onboarding approaches and are prepared to act on the result.

In the middle

The middle of a flow is where wait for trigger rules earn their place.

If the next message depends on a purchase, a tag from sales, or engagement with earlier content, hold contacts there (Mailchimp).

This is also where branching logic comes in.

If routing should depend on who the contact is, that is a conditional split, a separate rule that branches on up to five conditions rather than at random (Mailchimp).

For a deeper comparison of condition-based branching, see branch on email engagement or contact data.

Before a handoff to sales

If your flow ends by passing contacts to sales, a wait for trigger is often the right gate before the handoff step, so only contacts who meet your readiness condition move forward.

How you structure that moment is covered in choosing a marketing-to-sales handoff trigger.

When testing anything

Whenever you want to compare two treatments at the same step, replace the single action with a percentage split and put one version on each path (Mailchimp).

Keep the rest of the flow identical on both sides so the comparison stays clean.

Common mistakes and how to avoid them

• Using a percentage split to segment. A random split ignores who the contact is. If routing should depend on data or behavior, use a conditional split instead (Mailchimp).
• Using a wait for trigger when a simple delay is enough. If the only reason to pause is spacing, a time delay is simpler and easier to reason about (Mailchimp).
• Forgetting plan limits. In Mailchimp, percentage splits require a Standard plan or higher, and flows allow up to 10 wait for trigger rules (Mailchimp) (Mailchimp).
• Leaving tests unresolved. Decide up front when you will shift percentages toward the winning path (Mailchimp).
• Building waits with no exit plan. Know what happens to contacts who never meet the condition.

A quick decision summary

Rule selection is one layer of flow design.

The other is how the flow connects to your stack, from CRM data to reporting.

If that is your next question, see syncing your CRM with your automation, and the automation glossary defines the terms used here.

Finally, verify the exact capabilities and plan requirements in your own platform before building.

The behaviors described here reflect Mailchimp’s documented automation flows (Mailchimp); other tools implement the same concepts with different limits and naming.

How Meshline can help. Connect automation, Organic Marketing (demand generation), and customer lifecycle management (Revenue Intelligence).

Bring topic planning, content publishing and performance feedback into the conversation about your workflow. Book a Meshline demo.