PIING
Reading Piing: AlertsSegments and audiences
Piing: Alerts
- Getting started with Piing: Alerts
- Appearance and branding
- Create and manage notifications
- A/B testing
- Frequency capping and suppression
- AI notifications
- Web push
- Segments and audiences
- Signed-in vs signed-out targeting
- Automations
- Analytics and suggestions
- Integrations and data
- FAQ and troubleshooting
- Plans and billing
In this guide
- Two kinds of segment
- Build a rules segment
- VIP tier and store location
- How membership stays current
- Sync a Klaviyo or Ometria segment
- Example rules
Search or browse documentation
Piing: Alerts 8 / 14
Segments and audiences
Build audiences with rules on tags, metafields, VIP tier, spend, and browse intent, or mirror segments in from Klaviyo and Ometria.
Segments are smart collections for customers. A visitor's segments are resolved on every feed request, so notifications retarget the moment someone's data or behaviour changes. Open Audiences, then New segment to build one.
Two kinds of segment
- Rules: conditions on customer data and live behaviour, evaluated per request.
- Synced: a segment mirrored in from Klaviyo or Ometria. Needs the API key connected in Settings.
Build a rules segment
- Open Audiences, then New segment.
- Give it a Name and an optional Description.
- Leave Segment source on Rules.
- Set Match ALL conditions or Match ANY condition.
- Add conditions, then Save.
Each condition is a Field, an Operator, and a Value.
Note
conditions are grouped into customer, behaviour, and context. Starter saves customer conditions only. Behaviour and context conditions need Growth or Scale. See Plans and pricing.
Customer fields
Resolved from the synced customer record. These apply to signed-in customers.
- Customer tag (contains / does not contain), for example
VIP, store:london.
- VIP tier (equals / does not equal / exists).
- Store location (equals / does not equal / exists).
- Metafield (equals / does not equal / exists). Value format:
namespace.key or namespace.key=value.
- Total spent, Orders count, Days since last order (numeric comparisons).
- City, Country.
- Accepts marketing (true / false).
Behaviour fields
Resolved live from the first-party pixel, so they work for signed-out visitors too.
- Signed in (true / false).
- Viewed product and Viewed collection, by handle.
- Browse events (last 30d).
- Current cart value.
- Intent score (0 to 100).
See Signed-in vs signed-out targeting for how behaviour is tracked.
VIP tier and store location
Piing: Alerts derives two fields from your existing customer data:
- VIP tier comes from a
vip:<tier> tag (for example vip:gold) or a loyalty.tier metafield.
- Store location comes from a
store:<location> tag (for example store:london), set by your POS, loyalty app, or Shopify Flow.
Tag customers by these conventions and the fields populate on their own.
How membership stays current
Customer conditions recompute when Shopify sends a customers/update or orders/create webhook, so a customer joins or leaves a segment the moment their tags or spend change. Behaviour conditions evaluate live on each feed request. You don't re-run anything.
Why it matters: you define "shopped in London" or "spent over 500" once, and the audience keeps itself accurate.
Sync a Klaviyo or Ometria segment
- Connect the API key in Settings. See Integrations.
- Open Audiences, then New segment.
- Set Segment source to Klaviyo segment or Ometria segment.
- Pick the external segment to mirror.
- Save, then click Sync now on the Audiences list.
Members match to Shopify customers by external id, falling back to email against your customer cache. Synced membership applies to signed-in customers. Re-sync on a schedule with the ops endpoint (see Automations).
Example rules
Customer tag contains store:london
VIP tier equals gold
Days since last order greater than 90
Viewed collection contains dresses
Intent score at least 60
Related guides
Was this guide helpful?
Next guide in Piing: Alerts
Signed-in vs signed-out targeting
How the first-party pixel tracks browse intent, computes intent scores, and stitches identity from signed-out click to signed-in purchase.
Still need a hand? Contact us