The Audience module is where your customer data lives in Galantis. Every contact synced from Shopify, every list you build manually, and every segment defined by rules is managed here. Campaigns draw their recipients from this data. Automations evaluate conditions against it. Consent state is tracked within it. Understanding how contacts, lists, and segments relate to each other — and how they behave differently — is the prerequisite for building campaigns and automations that reach the right customers with the right message.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.
How audience data works in Galantis
Galantis syncs customer data from Shopify continuously via webhooks. When a customer is created, updated, or deleted in Shopify, the change is reflected in Galantis within seconds. This means your contact profiles, order history, tags, and consent status are always current — you are not working with a stale snapshot. On top of the synced contact data, Galantis maintains two types of audience groupings: Lists are static. You add customers to a list manually or via import and they stay there until removed. Lists are simple and predictable — useful for curated, stable groups like VIP customers or newsletter subscribers. Segments are dynamic. They are defined by rules evaluated against contact data. As customer data changes, segment membership updates automatically. A customer crosses your spending threshold — they join the high-LTV segment. A customer goes 60 days without ordering — they enter the lapsed segment. No manual management required.Guides in this section
Contacts
Customer profile fields, Shopify sync behavior, and related data available per contact.
Lists
Static customer groups — creating, managing, and using lists in campaigns and automations.
Segments
Dynamic rule-based groups — all available conditions, operators, and evaluation behavior.
Consent & Opt-outs
How opt-in status is tracked per customer and how opt-outs are handled.
How audience data feeds campaigns and automations
| Feature | Uses lists | Uses segments | Uses contact fields |
|---|---|---|---|
| Campaigns | As include/exclude targets | As include/exclude targets | For variable mapping in templates |
| Automations | As exclusion rules, trigger source (USER_ADDED_TO_LIST) | As exclusion rules, trigger source (USER_ADDED_TO_SEGMENT), condition evaluation | For condition evaluation, variable mapping |
| Back-in-Stock | — | — | For consent validation and notification delivery |
Related guides
- Campaigns — Audience Targeting — Using lists and segments as campaign audiences
- Automations — Exclusion Rules — Excluding lists and segments from automation enrollment
- Compliance — Opt-in & Consent — How consent state is enforced across the platform