Skip to content
Sign in Get started
Back to changelog
Email & SMS New

Three ways to split a flow

Not everyone who enters a flow should get the same thing. Flows now have three kinds of split, each answering a different question about the person in front of you.

Conditional split: who is this?

Branch on anything you know about the person when they reach the step.

  • What they’ve done. Placed an order, opened an email, viewed a product, any number of times, in any time window.
  • Who they are. Country, email status, when they signed up, and any custom profile property, like vip or favourite_food.
  • Where they belong. In or not in a segment.
  • Combine rules with all or any, in as many groups as you need.

Example: in a welcome flow, send people who already ordered a thank you, and everyone else a first order offer.

Trigger split: what started the flow?

Branch on the details of the event that started the flow, not the person’s whole history.

  • Every comparison you need. Equals, not equals, contains, greater than, less than, at least, at most.
  • Look inside lists. items.*.title contains hoodie matches an order where any item is a hoodie, and a list of collections contains “Sale” only when Sale is one of them.
  • Shown only where it works. The step appears for flows that start from an event, and lists that event’s own fields to pick from.

Example: after Placed order, send orders over £100 a VIP thank you, and orders with a new customer discount code a how to get started guide.

A/B split: which works better?

Send a share of people down path A and the rest down path B, from 1% to 99%. Each person always lands on the same path, and the step shows how many went each way so you can pick a winner.

Example: test a 10% discount against free delivery in an abandoned checkout flow.

See how each path performs

Every split shows how many people went down each path, right on the step, so you can see what your flow is doing at a glance.

Coming from Klaviyo?

The Klaviyo import (Settings, Marketing, Klaviyo import) brings your splits across as the same kind of split in Gro. Conditional splits keep their rules, trigger splits keep their conditions, with Klaviyo’s Shopify fields like $value and Collections renamed to Gro’s. Anything with no match in Gro is listed on the import page, so you know exactly what to check.

Get started

Open a flow, click + between two steps, and pick a split under Flow control. Read more in the flow builder guide.

Get an AI summary of Gro

Ask your assistant what Gro does, who it's for and how it's priced.