Documentation
Flow rules and condition fields
Updated 17 Nov 2026
A flow evaluates enabled rules by priority and sends the click to a path or a safe page. The built-in fields are 15 visitor properties plus token1–token10. Traffic-source parameters are extra fields. An enabled rule with no condition matches nothing.
Paths
Each path has a name, a rotation of weight or smart, and lists of landers and offers. Each entry is an id and a weight greater than zero. Exactly one path is the default. If you mark none, the first path becomes the default. The default is where a click lands when no rule matches.
Weighted rotation picks a lander and an offer with those weights. Smart rotation, together with the campaign’s bind_visitor flag, prefers a lander or offer this visitor has not already seen. Offer caps walk the path’s offers by sort order and skip a capped offer. The product stores a cap_fallback value on the offer, and the editor only offers next_offer. Routing does not read cap_fallback; a capped path ends in 404 when nothing is left.
A rule points at a path or at a safe page. The safe page must be an http or https URL. Rules are checked in ascending priority. Priorities in one flow must be unique. Save the flow as one document (GET or PUT /api/flows/{id}/doc). The simulator runs the saved document.
Condition fields
Conditions are a mode, and (the default) or or, and a list of { field, op, values }. These operators are the ones an enabled rule may use. The site’s “25 fields” are the 15 names below plus token1 through token10.
| Field | Operators on an enabled rule |
|---|---|
| country, device, language | in, not_in, eq |
| os, browser | in, not_in, eq, contains, not_contains, regex |
| region, city, isp | in, not_in, eq, contains, not_contains, regex |
| ip | in, not_in, eq, contains, not_contains, regex |
| referrer, user_agent | contains, not_contains, regex, in, not_in, eq |
| hour | between, in, not_in, gt, lt, eq |
| weekday | in, not_in, between, eq, gt, lt |
| is_bot, is_unique | is, eq, in |
| token1–token10, and parameters declared on a traffic source | in, not_in, contains, not_contains, eq, regex, gt, lt |
zone is always allowed as a source parameter. Other parameter names follow the editor’s pattern: a letter, then up to 39 letters, digits, or underscores.
Values
Country is two letters. Language is two or three letters. Device is mobile, tablet, desktop, bot, or unknown (empty user agent). Hour is 0–23, or HH:MM when the operator is between. Weekday is 0–6. between takes exactly two values. regex takes exactly one pattern, and that pattern must compile. is takes one JSON boolean, not the string "true".
An enabled rule must have at least one condition. At runtime, a rule with no conditions does not match. An enabled rule may contain at most three regex conditions in the whole flow; a regex past that budget does not match. A disabled rule can be saved unfinished and is not evaluated.
in / eq / contains / regex with several values match when any value matches. not_in / not_contains match when none match. A missing source parameter is an empty value, so a “not in” rule can match a click that simply did not send the parameter. Empty strings inside a value list are ignored.
The concepts page is how a matched path becomes a redirect.