How contextual conditions work
Contextual conditions are evaluated at request time against session context data including:- Geographic data: Country, state/province, city
- Customer attributes: Customer tags, account status, purchase history
- UTM parameters: Marketing source, medium, campaign
- Device information: Device type, operating system
- Shopping channel: Online store, mobile app, etc.
true for the current session, that rule is applied. Rules without contextual conditions always match and act as default/catch-all rules.
When multiple rules target the same collection, rules with contextual conditions are always evaluated before default rules. This ensures that a more specific conditional rule is never blocked by a default rule, regardless of creation order.
JSON Logic examples
Target US visitors:The contextual conditions form in the dashboard provides a user-friendly interface for building these JSON Logic expressions without writing code directly.
Case sensitivity
String-based condition operators (contains, does not contain, begins with, does not begin with, ends with, does not end with) are case-insensitive. A condition matching “klaviyo” will also match “Klaviyo” or “KLAVIYO”. This applies wherever contextual conditions are evaluated, including merchandising rules, search rules, sort orders, and block rules.