Audiences

An audience in Apphud is a group of users — either a built-in segment (Trial subscribers, Customers, Non-paying users, etc.) or a custom segment defined by filters on purchases, properties, experiments, attribution, or your own user properties. Use audiences to drill into who's in your app right now, bind paywalls per placement via Targetings in Mission Control, pick cohorts for A/B tests (run on a Targeting that uses the audience), and trigger messages or screens in Rules.

Find Audiences in the sidebar under Monetization setup → Users & Audiences.

Default vs. Custom audiences

The sidebar groups audiences into three views: All, Default, and Custom.

• Default — built-in segments that come with every app. They cannot be renamed, deleted, or updated. The exact list is below.
• Custom — segments you define yourself by combining filters. Custom audiences can be renamed, updated, or deleted, and saved from any filter combination via the Save audience… menu.
• All — both groups together.

Default audiences

Custom audiences

Custom audiences are filter combinations you've saved with a name. They drive dynamic content delivery elsewhere in Apphud:

• Bind paywalls per placement to an audience via Targetings in Mission Control.
• Run A/B tests on those Targetings to compare paywalls or full monetization schemes for the audience. A/B tests are not attached to an audience directly — they run on a Targeting, which uses the audience.
• Trigger messages, push notifications, or screens in Rules for users matching the audience.

Common use cases: discounted pricing for lower-income countries, extended trials for highly engaged non-converters, region-specific paywalls. Audiences can combine default user properties (Store Country, Locale, Language, Platform) with custom User Properties you set from your SDK.

Create a custom audience

You can create a custom audience in two places:

• From this page (the main route) — Users & Audiences is the canonical place to build, browse, and manage audiences.
• Inline from a Targeting — when setting up a Targeting in Mission Control, the audience picker lets you create a new audience inline without leaving the targeting flow. The audience is saved here in your library and behaves identically to one created on this page.

To create one from this page:

1. Pick a default audience to start from (or start from All Users).
2. Click Add filter + and combine the filters you need — see Filters below.
3. Click Save audience… → Save as new in the top right.
4. Give the audience a name and save. It appears in the sidebar under Custom.

Rename or delete a custom audience

Click the ⋯ menu on a custom audience in the sidebar:

• Rename audience — opens a dialog with the current name pre-filled. Edit and Save Changes.
• Remove audience — opens a confirmation dialog ("Are you sure you want to remove this audience? This action cannot be undone."). Click Remove audience to confirm.

Default audiences don't have a ⋯ menu — they can't be renamed or removed.

Update a custom audience

Open a custom audience, change the filters, then click Save audience… → Update selected.

Update selected is enabled only when the conditions hold:

1. The audience is custom (default audiences cannot be updated).
2. At least one unsaved filter is applied.

Otherwise the option is disabled with a tooltip explaining why.

Save as New

You can use an existing custom audience as a starting point for a new custom audience creation.
Open a custom audience, change the filters, then click Save audience… → Save as new.

Save as New option is enabled only when the conditions hold:

1. The View is set to filter only Production users.
2. At least one filter is applied.

Otherwise the option is disabled with a tooltip explaining why.

View / installed on

Three controls at the top of the page scope the audience preview:

View

Choose which user environment is included in the table:

• All users — production and sandbox together.
• Production users — only production.
• Sandbox users — only sandbox.

installed on

Standard date range with presets and a calendar — see Common controls → Period.

The range filters users by install date — the table shows users who installed the app within the selected period.

Search

The search field above the table searches by User ID.

Filters

Click Add filter + to scope an audience by additional parameters. Filters are grouped into seven categories.

Purchases

Properties

Experiments

User

Apphud Attribution

Attribution as computed by Apphud from SDK and integration signals.

MMP Attribution

Same parameter set as Apphud Attribution, but matched against attribution data received from connected mobile measurement partners (Adjust, AppsFlyer, Branch, Singular, Tenjin).

User Properties

Dynamic list of every system-reserved and custom User Property defined in your app (e.g., $age, $cohort, $email, $gender, $name, $phone, plus your own Facebook1, Google, QA_User_Property, …).

📘

Boolean filters

Filters like Autorenewal, Expires in next 24h, Is Customer, Has at least One Payment, Anonymous and Last Reinstalled in 24h expose a single value to select (e.g., Enabled, True). You pick it to match users who meet the condition — the filter can't be applied without choosing the value, and the opposite value isn't selectable.

For operator behavior, multi-select, predefined vs. free-form values, and chip mechanics, see Common controls → Filters.

Shared toolbar and table controls

The Users toolbar uses the same building blocks as other Apphud tables. Universal mechanics are documented once in Common controls; User-specific behavior is documented here.

From Common controls (same as elsewhere)

• Edit columns — toggle and reorder columns, or reset customization to defaults. See Reports → Edit columns.
• Auto-fit columns — fit widths to content. See Reports → Auto-fit columns.
• Sort — click a column header to sort. See Reports → Sort.
• Share URL — copy a URL that captures the current view. Events URL format: https://dash.apphud.com/<app>/share/e/<id>. See Reports → Share URL.

User-specific controls

• Refresh — the circular-arrow icon next to the search field. Click to pull users that arrived after you opened the page. New events do not stream in automatically.
• Export CSV — downloads the current filtered set as a CSV file. A confirmation dialog shows the exact row count: Export events (N). The export respects current filters, sort order, and visible columns.
• Pagination — at the bottom of the table:
  • Page navigation — 1–N of total with previous/next arrows.
  • Show per page — 50, 100, 250, or 500 rows per page.

Table columns

The table has one pinned column and several toggleable ones. Open Edit columns to change which are shown and to reorder them. Click Reset to default to restore the default set.

Pinned (always shown)

Toggleable

FAQ

Why is "Update selected" disabled?

One of three conditions isn't met: the audience is a default (predefined) one, no filter is applied, or you're in the sandbox environment. Switch to a custom audience, apply at least one filter, and confirm you're viewing production users.

Why do I see "Cannot delete segment with associated scheme" when removing an audience?

The audience is still referenced by a Targeting in Mission Control or by a Rule. A/B tests run on Targetings (not directly on audiences), so removing or reassigning the Targeting clears the audience's link to any active A/B test too. Apphud blocks deletion to prevent breaking those configurations. Remove every reference first (or reassign them to a different audience), then delete. See Rename or delete a custom audience for details.

Can I save a default audience under a new name?

Yes. Open the default audience, optionally add filters, and use Save audience… → Save as new. The new audience appears under Custom.

Where can I use a custom audience?

• As a Targeting audience in Mission Control — the Targeting picks paywalls per placement for users matching the audience.
• In A/B tests — tests run on a Targeting that uses the audience (not on the audience directly).
• In Rules — trigger messages, pushes, or screens for users matching the audience.

How do I find a specific Sandbox user?

Set View to Sandbox users (or All users) and paste the User ID into the search field. The date range and any applied filters are ignored during search — only the View selector affects what's searched. With View set to Production users, sandbox users won't be found.

How do I share a saved view with my team?

Click the Share URL icon in the top-right of the table. Apphud generates a URL that captures your audience selection, filters, sort, and column setup.

Why doesn't my user show up after I set a custom user property?

When you target an Experiment to a custom audience defined by custom user properties, set and flush properties back-to-back — call Apphud.setUserProperty(...) immediately followed by Apphud.forceFlushUserProperties. Audience matching happens server-side using the latest stored values; a gap of more than ~2 seconds can cause the user to miss the intended audience. See Audience Based on User Properties.