Audience filtering
Decide exactly who sees a form using targeting rules evaluated before it loads.
Audience filtering controls who sees a form. Before a form renders on your storefront, Formtoro checks whether the current visitor matches the form's audience. If they match, the form appears; if not, it stays hidden.
You build an audience in the Audience panel of the builder. It's a set of conditions combined with AND / OR groups — exactly like a segment.
What you can target
| Group | Targets |
|---|---|
| Page & campaign | Page path, full URL, UTM source, UTM medium, UTM campaign |
| Device & location | Device type, country, continent, EU visitor |
| Visitor | New visitor, returning visitor, has subscribed, any visitor |
| Storage | A cookie, local storage, or session storage value (by key) |
A few examples:
- Show a welcome offer only to new visitors on the homepage.
- Show a campaign form only when UTM campaign contains
spring-sale. - Show a mobile-friendly banner only on device type = mobile.
- Suppress a form when a cookie like
vipis set.
Operators
Depending on the target, you can use:
- equals / does not equal
- contains / does not contain
- is one of / is not one of (match any value in a list)
- is set / is not set (the value exists or not)
- greater than · ≥ · less than · ≤ (numeric)
For cookie, local storage, and session storage targets, you also provide the key (the name of the cookie or storage entry) to read.
Combining conditions
Conditions live in AND or OR groups, and groups can nest. All children of an AND group must match; at least one child of an OR group must match. This lets you express rules like:
(Device is mobile) AND (Page path contains
/productsOR UTM campaign containslaunch)
How it runs
When a shopper loads a page, the storefront widget asks Formtoro whether the form is eligible. Formtoro evaluates the whole audience against the visitor's context and only renders the form on a match. Storage-based conditions (cookie/local/ session) are checked in the browser; the rest are evaluated on the server during the eligibility check.
Test your audience
The audience tester lets you check a rule before publishing. It shows input fields only for the targets your rules actually use — enter sample values (a page path, a device type, a UTM value, a cookie value) and it tells you whether the audience matches, with a per-condition breakdown of what passed and what failed. Like the logic simulator, it works from the runtime inputs you provide; there are no preset visitor personas.
Next steps
- Logic engine — adapt the form after the right audience opens it.
- Display & triggers — how and when an eligible form appears.