Last updated: March 2026 Category: Segments
Overview
BeyondCart provides over 20 rule types for building segments. Each rule type targets a specific aspect of user behavior, order history, or profile data. This reference explains every available rule type with practical examples.
Prerequisites
Familiarity with the segment builder (see Creating a Segment)
An understanding of AND/OR combinators
Key Concepts
Rules are the building blocks of segments. Each rule consists of three parts:
Rule type — What data point to evaluate (e.g., Total Orders).
Operator — How to compare the value (e.g., is greater than, equals, contains).
Value — The threshold or match target (e.g., 5, "shoes," 2026-01-01).
Step-by-Step Guide
Below is every rule type organized by category. For each rule, you will find a description and an example.
Order-Based Rules
Total Orders — The total number of orders a customer has placed. Example: Total Orders is greater than 3 targets customers with 4+ orders.
LTV (Lifetime Value) — The total amount a customer has spent across all orders. Example: LTV is greater than or equal to 500 targets customers who have spent $500 or more.
AOV (Average Order Value) — The average dollar amount per order. Example: AOV is between 50 and 150 targets mid-range spenders.
Last Order Date — The date of the customer's most recent order. Example: Last Order Date is before 90 days ago targets customers who have not ordered in the last 90 days.
Avg Days Between Orders — The average number of days between consecutive orders. Example: Avg Days Between Orders is less than 30 targets frequent buyers.
Order-based (custom) — Advanced order filtering with custom criteria such as specific order tags, fulfillment status, or discount codes used.
Product Interaction Rules
Viewed Products — Products the user has viewed in the app. Example: Viewed Products contains "Summer Dress" targets anyone who viewed that product.
Purchased Products — Products the user has purchased. Example: Purchased Products contains any of "Sneakers, Running Shoes" targets buyers of either product.
Not Purchased Products — Products the user has never purchased. Example: Not Purchased Products contains "Premium Plan" targets users who have not bought the premium plan.
Added to Cart — Products the user has added to their cart (regardless of purchase). Example: Added to Cart contains "Wireless Earbuds" targets users who showed purchase intent for that item.
Not Added to Cart — Products the user has never added to their cart. Example: Not Added to Cart contains "Gift Card" targets users who have never considered gift cards.
Has in Wishlist — Products currently in the user's wishlist. Example: Has in Wishlist is not empty targets users with at least one wishlisted item.
Engagement Rules
Has App Session — Whether the user has opened the app within a given time frame. Example: Has App Session in the last 7 days targets recently active users.
Profile Rules
Email — The user's email address. Example: Email contains "@company.com" targets users with a company email domain.
Phone — The user's phone number. Example: Phone starts with "+1" targets users with a US phone number.
First Name — The user's first name. Example: First Name is not empty targets users who have provided their first name.
Last Name — The user's last name. Example: Last Name equals "Smith" targets all users with that last name.
Registration Date — When the user account was created. Example: Registration Date is after 2026-01-01 targets users who signed up this year.
Is Paying Customer — Whether the user has placed at least one order. Example: Is Paying Customer equals true targets all buyers.
Birthday — The customer's birth month and day (no year is stored). Several variants are available: Birthday is today targets customers whose birthday is today; Birthday in next N days targets the upcoming birthday window; Birthday month equals X targets everyone born in a specific month; Has birthday on file sizes the audience that has provided a birthday. See Birthday Capture and Targeting for the full guide.
Advanced Rules
Customer Metafield — Match against custom metafields synced from Shopify. Example: Customer Metafield loyalty_tier equals "Gold" targets gold-tier loyalty members. You specify the metafield namespace and key, then set the operator and value.
Tips and Best Practices
Combine order and engagement rules for powerful segments. For example, "LTV > $200 AND Has App Session in last 14 days" identifies your most valuable active users.
Use product interaction rules for retargeting. "Viewed Products contains 'Winter Jacket' AND Not Purchased Products contains 'Winter Jacket'" targets users who browsed but did not buy.
Leverage metafields to bring Shopify-specific data (loyalty tiers, custom tags, subscription status) into your segmentation.
Test with Preview after adding each rule to see how membership changes incrementally.
FAQ
Q: Are product rules based on product titles or IDs? A: Product rules match against product titles by default. You can also match by product collection or product tags depending on the rule configuration.
Q: How far back does behavioral data go? A: BeyondCart retains behavioral data (views, cart additions, sessions) from the moment you install the app. Historical order data is synced from Shopify.
Q: Can I use multiple operators on the same rule type? A: Yes. For example, you can add two "Total Orders" rules — one with is greater than 2 and another with is less than 10 — combined with AND to target a specific range.
Q: What happens if a metafield does not exist for a user? A: Users without the specified metafield will not match the rule. They are treated as not having a value for that field.
Related Articles
