Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.digifist.com/llms.txt

Use this file to discover all available pages before exploring further.

Customer Segments are dynamic groups defined by rules evaluated against contact data. Unlike lists, which are maintained manually, segments maintain themselves — as a customer’s orders, spend, engagement, or tags change in Shopify, their segment membership updates automatically. This makes segments the right tool for any audience group defined by behavior, lifecycle stage, or data thresholds. Segments are used as campaign audience targets, automation triggers, automation condition evaluations, and automation exclusion rules — they are woven into nearly every part of the Galantis platform.

​
What this covers

  • How segment rules work
  • All available rule conditions and operators
  • AND/OR grouping for complex rule logic
  • How segment evaluation works
  • Using segments in campaigns and automations

​
How segment rules work

A segment is defined by one or more rule conditions. When Galantis evaluates a segment, it runs the rules against every customer in your workspace and identifies which customers match. Customers who match become members; customers who no longer match are removed. Rules use two levels of logic:
  • AND logic within a group — all conditions in a group must be true for a customer to match that group
  • OR logic between groups — a customer who matches any group is included in the segment
This structure allows complex expressions like: 
(Total spent > 500 AND Country = MX)
OR
(Orders count >= 3 AND Consent = Yes)
A customer who matches either group is a segment member — they do not need to match both.

​
Rule conditions

Phone number — Match customers by exact phone number.
OperatorBehavior
exact matchCustomer’s phone equals the specified value
Added to list — Match customers who are members of a specific Customer List.
OperatorBehavior
in listCustomer is a member of the selected list
The Added to list condition creates an intersection between a dynamic segment and a static list — useful for applying additional rule-based filters on top of a manually curated list.

​
Full rule condition reference

RuleAvailable operators
Phone numberexact match
Added to listin list
Last message receiveddate comparison
Last engaged atbefore / after / between / in last X days
Orders count>, <, >=, <=, =, between
Total spent>, <, >=, <=, =, between
Days since last order>, <, >=, <=, =, between
Days since first order>, <, >=, <=, =, between
Average order value>, <, >=, <=, =, between
Countryis / is not / in / not in
Languageis / is not / in / not in
Consent statusis / is not (Yes / No / Unknown)
Purchased collectionin / not in
Purchased brandin / not in
Purchased price rangebetween / not between
Messages received>, <, >=, <=, =, between
Messages read>, <, >=, <=, =, between
Automation completions>, <, >=, <=, =, between
Lifecycle stageis / is not / in / not in

​
How segment evaluation works

When a segment is evaluated, Galantis runs the rule query against all customer records, syncs the membership pivot table, and emits UserAddedToSegment events for customers who newly match the rules — customers who matched before evaluation and still match do not generate a new event. This event-driven mechanism is what powers the USER_ADDED_TO_SEGMENT automation trigger. When a customer’s data changes — a new order pushes them over a spending threshold, a tag is added, days since last order increments — the next segment evaluation detects the membership change and fires the trigger for that customer.

​
Building effective segments

A high-LTV lapsed buyer segment 
Total spent > [your LTV threshold]
AND Days since last order > 60
AND Consent status = Yes
Pairs with the VIP Win-Back automation recipe. A first-time buyer cross-sell segment 
Orders count = 1
AND Days since last order < 14
AND Consent status = Yes
Customers who made their first purchase in the last 2 weeks — a high-intent window for a second-purchase prompt. A Mexico high-spend segment 
Country = MX
AND Total spent > 500
AND Consent status = Yes
Market-specific high-value audience for a localized campaign. A re-engagement suppression segment 
Last engaged at > 90 days ago
AND Messages received > 5
Customers who have received multiple messages but haven’t engaged in 90 days — useful as a campaign exclusion to protect deliverability.

​
Best practices

  • Always include Consent status = Yes in segments used as campaign audiences. This ensures the segment only contains SUBSCRIBED customers and prevents the consent filter from silently reducing your reach at send time.
  • Use segments as automation exclusions for active sequence participants. If a customer is enrolled in a post-purchase sequence, a segment defined as Automation completions < 1 for [post-purchase automation] can be used as an exclusion to prevent them from being enrolled in a separate re-engagement flow simultaneously.
  • Name segments clearly and include the defining criteria. High LTV Lapsed - MX - >500 spent is more useful than Segment 3 when you are selecting an audience in the campaign builder.
  • Build and verify segments before referencing them in automations. A segment used as a trigger source or exclusion rule should have its membership count and rule logic confirmed before the automation is activated.
  • Do not over-segment. A large number of similar, slightly different segments becomes difficult to maintain. Prefer fewer, well-defined segments that cover clear lifecycle stages or targeting needs.