Skip to content
Releaseo

Create audience segments

Build conditions with AND, OR and NOT, save them as an audience group, and use them to target changelog posts, roadmap items and in-app launches.

A segment is a saved set of conditions that describes a group of users, such as "plan is Pro and country is Germany". You build and save segments on the Users page, then reuse them as audiences. Releaseo's sidebar calls the saved result an audience group.

Build conditions

  1. Open Audience → Users.

  2. Select Conditions to expand the builder.

  3. Choose Add condition and pick a source:

    • User property: attributes on the user profile, such as plan, country or signup date.

    • Event: what a user has done, how often, and when.

    • In-app launch: impressions, views, clicks and dismissals of your in-app launches.

    • Changelog: posts a user opened or saw in the changelog widget.

  4. Complete the row: pick the property, an operator such as "is", "is not", "contains", "is at least", "is any of", "is known", and a value.

  5. Select Run query to see matching users in the table. The audience summary above the table estimates the size.

Until you add a condition, the builder says "Everyone matches. Add a condition to narrow it down."

Combine with AND, OR and NOT

The top group reads Match All of the following or Match Any of the following.

  • All means every condition must be true (AND).

  • Any means at least one must be true (OR).

  • Add group nests a group inside the first, so you can mix both, for example "plan is Pro AND (country is Germany OR country is France)".

  • Negate this group (NOT) flips a nested group so it matches users who do not meet it. Each nested group has this toggle.

Groups can be nested up to three levels, and a group holds up to 20 items.

Behaviour conditions

Event, In-app launch and Changelog conditions look at what users did. They offer choices such as "did", "did not", "did for the first time", "did for the last time" or "did, how many times", with a time window such as "at any time", "in the last N days", or "between" two dates. Behaviour conditions need a saved audience group when used to target content, so save the segment first.

Save a segment

  1. With at least one condition added, select Save segment. If the button is disabled, add a condition first.

  2. Enter a Segment name. If a saved segment is selected, choose Create new or Update selected under Save as.

  3. Confirm with Save segment or Update segment.

Saving needs the Static data manage permission. Your saved segments are listed in the Segments rail on the Users page (Saved segments). Select one to apply it, or All users to reset.

Saved segments are also listed under Static data → Audience groups, where drafts can be published, previewed or deleted. Published groups are listed first wherever you pick an audience.

Where segments are used

When you target content, you choose an audience mode:

  • All users: everyone who can see the surface.

  • Saved audience: use a published audience group. Required for behaviour conditions.

  • Custom condition: build conditions just for this item.

This choice appears in the Audience tab of changelog posts, and in roadmap items and in-app launches.

Audience targeting is evaluated when the widget requests content. Conditions are checked against the traits sent with the request, so only identified users can match property conditions.

Troubleshooting

  • A property is missing from the list. It appears after a user with that trait has been identified. Check Static data → Audience fields.

  • An audience shows fewer or more users than expected. Behaviour-based audiences are calculated in the background, so delivery can lag slightly behind the preview.

  • Saved conditions could not be read. If a post warns that saved conditions could not be read, rebuild them before saving. Publishing as-is would show the update to everyone.

Was this article helpful?

Still stuck? Contact us and mention this article.