How rules combine
Rules are additive: every rule on an offer must pass for it to show. Adding a rule narrows the audience, never widens it. There's no “any of these” grouping across different rule types — if you need either/or logic, that's two offers with complementary rules.
Most rules take an include list and an exclude list, and exclude wins. That lets you write “customers tagged VIP, except in these markets” as one rule instead of two. An empty include list means no restriction rather than “match nothing”, so exclude-only rules work fine.
Within a single rule, a list is an any-of match — a shopper in any one of three Klaviyo segments passes. Across rules it's all-of. That combination is what lets one offer describe a broad audience narrowed on several axes at once.
What you can express
Because rules compose, specificity is a matter of stacking two or three of them:
- “Shoppers in the EU market, with more than €80 in cart, who aren't tagged wholesale” — Markets + Cart Value + Customer Tags (exclude).
- “Anyone viewing a product in the Cameras collection, on mobile, who doesn't already have a memory card in their cart” — Trigger Collections + Device Type + Cart Products (exclude).
- “Subscription customers in Canada, during the first week of December” — Subscription in Cart + Shipping destination + Date & Time Scheduling.
- “Shoppers from paid traffic who haven't applied a discount code” — Traffic Source + Discount Code Applied.
None of those need custom code, a second app, or duplicate offers.
Cart contents
| Rule | What it targets | Include / exclude |
|---|---|---|
| Cart Products | Specific products in the cart | Both |
| Collections | Cart contains a product from given collections | Both |
| Specific Product Variants in Cart | Exact variants, not just the parent product | Both |
| Product Tags | Tags on products in the cart | Both |
| Cart Attributes | Custom cart attributes — gift message, delivery date, anything your theme writes | Both |
| Subscription Products | Specific subscription products in the cart | Both |
| Subscription in Cart | Whether the cart contains any subscription at all | Required / none |
Cart value and quantity
| Rule | What it targets | Include / exclude |
|---|---|---|
| Cart Value | Total cart value | Minimum and maximum |
| Collection Cart Value | Spend within given collections, or the whole cart | Minimum and maximum, and several conditions can stack |
| Cart Product Quantity | Units of given products or collections — countable across all lines, or only subscription or only one-time lines | Minimum and maximum, and several conditions can stack |
Audience
| Rule | What it targets | Include / exclude |
|---|---|---|
| Markets | The Shopify Market being browsed | Both |
| Shipping destination country | Where the order is actually going | Both |
| Customer Province / State | Sub-national region | Both |
| Customer Tags | Shopify customer tags | Both |
| Klaviyo Segment | Klaviyo segment membership, from a synced copy rather than a live API call | Both, plus a choice of how to treat unknown membership |
| Customer Language | Shopper's language, with base-language fallback | Both |
| Device Type | Mobile or desktop | Both |
| B2B / Wholesale | Whether the customer is a B2B buyer | Both |
| Retail Locations | Which physical store — point of sale only | Both |
Trigger — product page only
| Rule | What it targets | Include / exclude |
|---|---|---|
| Trigger Products | The specific product being viewed | Both |
| Trigger Collections | Any product from given collections being viewed | Both |
These are the only rules that read the page itself rather than the cart, which is why they're specific to the product page — and why genuine pairing logic lives there.
Context
| Rule | What it targets | Include / exclude |
|---|---|---|
| Date & Time Scheduling | Date range, days of the week, specific dates and hour windows | Range, plus include/exclude per dimension |
| Discount Codes | Which codes are applied to the cart | Both |
| Discount Code Applied | Whether any code is applied at all | Presence |
| Traffic Source | Where the shopper arrived from | Both |
A few behaviours worth knowing
Language matching falls back by base language. A shopper on en-DE matches a rule targeting en. Target en-US and you'll match en-US and en, but not en-DE.
Discount codes match case-insensitively, because Shopify treats them that way and shoppers type any casing.
Scheduling runs in local time, and its four dimensions combine — so a weekend promotion, a specific date, and an hours window can all apply to one offer. Hour windows may wrap past midnight, so a 10pm–2am deal is one window rather than two.
Klaviyo membership can be unknown, and you decide whether unknown counts as in or out rather than the app guessing.
The same rules target more than offers
This isn't an offers-only feature. The identical targeting engine, with identical semantics, also governs reward programs and checkout customizations — so a condition means the same thing wherever you apply it, and you learn it once.
