Condition Nodes

Condition nodes route visitors based on rules. This one sends mobile and tablet visitors to one page, US and Canada visitors to another, and everyone else down the Default Route:

Use them when you want different visitors to take different paths based on country, device, browser, ISP, connection type, language, referrer, or captured tracking-field data.

If you only want a percentage split, use a rotator node instead.

What conditions do

When a visitor reaches a condition node, FunnelFlux checks the routes in the condition and sends the visitor down the first route that matches.

If no route matches, the visitor goes down the default route.

This lets you build logic such as:

• mobile visitors go to one lander, desktop visitors go to another
• US traffic goes to one offer, non-US traffic goes elsewhere
• traffic from a specific source or placement gets a special path
• visitors with a captured URL parameter value get routed differently

Routes, rule groups, and rules

Conditions have three layers. To see all three, hover over the condition and click the edit button, or double-click it. That opens Condition Settings:

Routes [1] are the outgoing paths from the condition node. Routes are evaluated in the order shown under Route Priority, and you drag them to reorder. The Default Route is pinned at 0 and has no rules.

Rule groups [2] are groups of rules inside a route, added with + Add group.

Rules [3] are the individual checks, such as country is US, device is mobile, or tracking field contains a specific value. Add them with + Add rule.

This structure matters. If you want to match "US + Android" OR "Canada + iOS", you should use separate rule groups rather than putting all rules into one group.

Local vs global conditions

Condition nodes can be local or global. The tag at the top right of Condition Settings [4] shows which one you are editing.

Local conditions exist only inside one funnel. Use them for logic specific to that funnel.

Global conditions can be reused across funnels. If you edit a global condition, the change applies everywhere it is used.

Global conditions are useful for reusable routing rules, such as mobile vs desktop routing, blocked geos, or common ISP/device handling.

Common mistakes

The most common mistake is using a condition when a rotator would be simpler.

Use a condition when the visitor needs to match a rule. Use a rotator when you only want a weighted split.

Another common mistake is putting too much logic into one route. If a condition becomes hard to read, split it into clearer routes or use multiple condition nodes.

For a deeper walkthrough, see Using conditions.

Updated on: 13/10/2026