Audience
Understand, segment, and target your app's users.
Audience
The Audience section is where you understand who your users are and define which groups should see specific flows. Every end user who interacts with your app through the Setgreet SDK becomes part of your audience automatically.
End users
An end user is anyone who opens your app with the Setgreet SDK installed. Users are identified in two ways:
- Anonymous users -- the SDK generates a unique anonymous ID for every device. Flows can target anonymous users, but you cannot attach custom attributes until the user is identified.
- Identified users -- when your app calls the SDK
identifyUsermethod with a user ID and optional attributes, the user becomes a known individual you can target with precision.
Once identified, users carry attributes like plan, signupDate, or completedOnboarding that you define and send from your app.
Segments
Segments let you group users by shared characteristics. A segment is a reusable set of conditions -- for example, "users on the Pro plan who signed up in the last 30 days." You build segments in the dashboard with the condition builder. All conditions in a segment are combined with AND: a user must match every one of them to be included.
Segments are used in flow triggers to control which users see a flow, so you can ship different experiences to different audiences without writing conditional logic in your app.
How targeting works
When the SDK checks whether a flow should display, Setgreet evaluates the flow's trigger conditions against the current user's attributes and events on the server, then returns the matching flow. Because targeting is evaluated server side, you can change who sees a flow without shipping an app update.
| Concept | Purpose |
|---|---|
| User Attributes | Key-value data about each user, used for personalization and targeting. |
| Segments | Reusable groups of users defined by attribute and behavior conditions. |
User attributes and segments are only as useful as the data your app sends. Make sure to call identifyUser with
relevant attributes after login and whenever key user properties change.