Concepts
Audiences and segments
Who a campaign reaches, and how to describe that group.
An audience is the set of people a campaign or journey is meant for. Sapagan resolves it when the message is planned, and removes anyone who cannot be messaged. The reasons are recorded: unsubscribed, no consent for the store, suppressed address, no device or address.
Segments#
A segment is a saved audience built from conditions on attributes and events. Operators build it in the console. The API can read and count them:
GET /v1/segmentslists the workspace's segments.GET /v1/segments/fieldslists what a condition can use in this workspace.POST /v1/segments/countcounts a definition live, saved or not.
A campaign built from a segment uses the people who match when it sends.
People counts#
GET /v1/workspace/overview shows totals: people, push devices, events and, for marketplaces, stores. Counts for a segment include how many can actually be reached, because reach is smaller than the match when people have no device or have opted out.
Marketplace audiences#
In a marketplace, a store never builds "everyone". Its audience is one of a closed set tied to relationships with that store: buyers, followers, lapsed buyers, repeat buyers, and a few others such as product viewers. The engine resolves it inside the store's own scope, with the store's own consent, and applies the store's reach cap. See Stores.
Test audiences#
A test send goes only to test people: the list under Settings, Setup, "Test people" (GET /v1/setup/test-people). Use it to try a campaign or a journey on yourself.