Segments
Segments group players — the targeting primitive for campaigns and journeys.
Dynamic vs static
- Dynamic — defined by rules over player attributes, behaviour, and financials. Membership is computed and kept up to date automatically.
- Static — an explicit list you manage by hand (add/remove players).
Building a dynamic segment
- Segments → New.
- Add rules — attributes (country, language, custom fields), lifecycle stage, financials (LTV, deposits), and behaviour (events matched).
- Combine rules with AND/OR.
- Watch the live count preview update as you edit — you see how many players match before saving.
- Save. Rules remain editable afterwards.
Static segments & manual members
For a static segment, add or remove individual players directly. Useful for curated lists (e.g. a hand-picked VIP invite).
Real-time membership
A dynamic segment can opt into real-time membership: a fast worker job reconciles recently-changed players against real-time segments in about 30 seconds, so membership tracks player activity closely. A periodic full recompute remains the backstop against drift.
Exporting & syncing
- Export as audience — download a segment as CSV, or hit the API endpoint
(
/api/v1/segments/{id}/export). - Scheduled exports — configure recurring exports that the worker emails as CSV on a schedule.
Using a segment
- Campaigns target a segment (with optional control groups).
- Journeys can enrol a segment or use segment membership in conditions.
- Overlap analytics show how segments intersect over time.