How do I branch an automation by funnel or page visited?
Add a condition from the Funnel and pages group inside the Router (or Condition) step and branch the automation by the contact's browsing — whoever visited the pricing page gets one message, whoever didn't gets another. This is how you act on demonstrated interest without relying on a manual tag or on a segment that only refreshes once a day.
These are the same conditions already available in the contact filter, now available inside the flow.
Role: any member with edit access to the workspace.
Before you start
- A published or in-progress automation with at least one trigger.
- A published page or an existing funnel.
- Browsing only matches when the visit was recorded in the contact's history. An anonymous visit — by someone who was not yet a contact when they browsed — does not match; see the Origin and history match different things section below.
Steps
-
On the automation canvas, click the + where the split should go and choose Router.
-
On path 1, give it a name that states the intent (for example,
Saw pricing) and click Add condition. -
In the left column of the menu, open the Funnel and pages tab.
-
Choose the condition:
-
The field opens a searchable selector — type to filter and check as many pages (or funnels) as you want. The operators are is one of and is not one of, so a single path can cover an entire list.
-
Repeat on the other paths. Use Add path to create more (up to 10).
-
Connect each path's output to the step that should run, and also the Otherwise output — that's where contacts that match no path leave.
The funnel selector lists funnels from both generations in the same field, so you don't need to know which one the funnel was created in.
Origin and history match different things
The four conditions look like two, but they answer different questions — and picking the wrong one is the most common reason a path stays empty.
- Visited this page? and Came through this funnel? read the history: every visit and every capture recorded for that contact. A contact who already existed and came back through another page matches on it.
- Origin page and Origin funnel read the first touch: the page and funnel recorded when the contact was created, never rewritten afterwards. A contact who already existed and was re-captured on a new page does not match on it.
When in doubt, use Visited this page? — that's the one that answers "did this contact show interest in this".
In both cases the visit must be linked to the contact. Someone who browsed the pricing page before leaving an email or phone number only starts having history from the moment they become a contact; the visit before that is not considered.
If it didn't work
- Every contact falls into Otherwise: check whether you used the origin condition where you wanted the history one. Swap Origin page for Visited this page? and test again.
- A contact you know visited doesn't match: the visit most likely happened before they became a contact. Only browsing after identification enters the history.
- The automation won't publish: the builder warns when a condition is incomplete — leaving the page or funnel selection empty counts as incomplete.
- The chip shows "Item removed": the selected page or funnel was deleted. The filter still applies, but nothing matches that item any more — remove the chip and pick another.
- The contact took the wrong path: with One path, the first matching path wins, top to bottom. Reorder the paths or switch to Multiple paths.
Related
- How do I branch an automation by a quiz answer? — branch by quiz and form.
- How do I branch an automation by product purchased? — branch by what the contact already bought.
- Automations — how a flow works end to end.