Skip to content
DocsSearch the docsEnglishBack to siteOpen console

Audiences and destinations

An audience is a saved definition of a group of people on one website — who did what, how often, in which order, and who to leave out. AdPix keeps its membership materialized and refreshes it on its own, so the size you see is the size you push, and a destination receives identified members only.

What an audience is#

An audience is a named group of people on one website, described by rules rather than by a list: "added to cart and did not purchase within 3 days", "bought for more than 20 in the last 90 days", "mobile visitors from paid search". AdPix turns the rules into a membership list, keeps that list up to date, and lets you use it in three places:

  • Reports — add the audience as a comparison on any report or on Realtime. See Comparisons.
  • Overlap — see how two or three audiences intersect. See Audience overlap.
  • Destinations — push its identified members to a CRM or any webhook.

The pages live under Activate in the sidebar, starting at /audiences.

Premium feature

Audiences is not open on the Free plan. Anyone who can view the website's reports can open audiences; creating, editing, refreshing, deleting and pushing need the edit-audiences permission (marketer and above). A condition or breakdown on an identifier — a CRM list, or an email, phone or name sent with an identify call — also needs the Identifiers permission, and people without it see those values masked as •••.

The audiences list#

The audiences list with size, 28-day trend and destinations.
The audiences list with size, 28-day trend and destinations.

/audiences lists every audience on the website, ordered by name. Each row shows:

Column What it means
Audience name, a one-line summary of the rules, and badges such as Sequence or Exclude
Users people currently in the audience
Trend and change a 28-day sparkline, and the change against the first day of that window
Destinations where the audience is pushed
Created when and by whom

The header counts how many audiences the website has out of its limit of 100, and how many people are in at least one audience compared with all users in the selected range. The tabs filter by kind: All, Synced (linked to a destination), Sequences, and Predictive, which is marked Soon — predictive audiences are not available yet.

From here you can open the Overlap report, export the list as CSV, or select New audience.

Start a new audience#

New audience opens /audiences/new, with four ways in:

  • Custom — an empty builder.
  • Suggested — ready-made audiences sized on your own data over the last 28 days, each with its approximate size. A suggestion that needs an event your website has not recorded in 28 days says which event is missing and shows no size.
  • Templates — the same set, opened in the builder so you can change them before saving.
  • Describe it (Beta) — write the audience in plain words and get conditions back. It is unavailable when the website has no AI key configured.

The suggestions are: cart abandoners, purchasers, repeat purchasers, purchasers inactive for 7 or 14 days, site searchers, new users in the last 7 days, engaged non-converters, and paid search visitors.

Build the rules#

The builder at /audiences/build (and Edit definition on an existing audience) has two halves: who to include and who to exclude.

Include groups#

Each include group holds up to ten conditions and says whether all or any of them must hold. Add more groups with or: a person who satisfies any include group is in. Each group also has a scope:

Scope The group holds when…
User the conditions hold over everything the person did in the window, across sessions
Session one session satisfies the conditions on its own
Event one single event satisfies every condition (only event and dimension conditions)

Condition types#

Type Example Notes
Event did purchase at least 2 times in the last 30 days count with ≥ > = ≤ <; = 0 means "did not do it"; up to three parameter filters on the same event, such as value ≥ 20
Dimension device category is one of mobile, tablet channel, source, medium, campaign (first and session), country, region, city, device, browser, OS, page path, page title, hostname, event name, network operator, network type, language, or a custom event parameter
Sequence added to cart, then did not purchase within 3 days 2 to 6 steps in order within 1–90 days; only the last step can be "did not"
CRM trait plan is not one of free identified people only; the builder shows how many profiles carry the trait
Audience is a member of Purchasers membership of another audience on the same website, or not

Dimension and parameter matching is exact: is one of, is not one of, contains, starts with, and numeric greater / less than. There is no regular-expression match. A dimension name the server does not recognise is rejected with an error that names the condition — a typo can never turn an audience into everyone.

Exclude groups#

An exclude group removes people who match it. A temporary exclusion is evaluated over the membership window, so someone who stops matching comes back in. A permanent exclusion looks at all history: once matched, never a member — for example "ever refunded".

Membership duration#

Membership duration (1–540 days, default 90) is the look-back: a person must have at least one event in that window, and it is the default window for every condition that does not set its own.

The live estimate#

While you edit, the panel on the side recomputes the audience about half a second after each change:

  • Users and the share of all users on the website.
  • Weekly bars — when members were first active, over 14 weeks.
  • Overlap with your ten largest saved audiences, and a note when the new audience is the same as, inside, or contains one of them.
  • Push to — the destinations the audience will feed after saving. Google Ads and Meta are listed as Soon.

The estimate runs the same query as the saved audience, so the number you save is the number you saw.

Select Save audience. AdPix computes membership immediately; if that takes longer than 30 seconds the audience shows Computing and finishes in the background. After that it refreshes on its own schedule (every 15 minutes by default).

The audience page#

Opening an audience shows /audiences/<id>:

  • Headline figures for the selected range: users and devices, people who joined and left (a person counts once, however many devices they use), the share of members active in the range who converted in it (next to the same rate for everyone), and the revenue those conversions brought.
  • Size trend — one point per day, with a marker wherever the definition was edited.
  • Composition — how members split by a dimension (device, country, channel …), with an index against all users: 150 means members are one and a half times as likely to have that value as everyone else.
  • Definition — the rules as readable chips, and the edit history.

Buttons take you to Overlap, add the audience as a Compare on the reports, or Edit definition.

Users and devices

Users counts people: signed-in activity from several devices counts once. Devices counts distinct browsers and apps, which is what the standard reports call users. That is why an audience of 120 users can show 140 devices, and why comparing an audience on a report counts devices.

Destinations#

A destination is the system members are sent to. It is created under Admin → Integrations, not on this page, and comes in three shapes:

Type What it receives
Generic webhook a POST with a JSON body to your URL
WHMCS — companion addon the same body, to the addon's receiver on your WHMCS install
WHMCS — admin API a call to WHMCS's own API that writes the client's custom fields

An audience can use any enabled destination of its organisation that is not tied to a different website; anything else is refused. Method, custom headers and HMAC signing are covered in Webhooks and HMAC signing.

Pushing members#

There are two ways to send members:

  • Link a destination (Push to). The first refresh after linking sends every current member; after that, each refresh sends the people who joined since the last successful sync. Someone identified after joining reaches the destination with Activate.
  • Activate — send every current member to one destination now.

Either way only identified members leave AdPix — people linked to a sign-in, an email, a phone number or a CRM customer ID. Anonymous visitors, and visitors AdPix only recognised by device, are never sent. Every identified member is queued, one delivery per person; there is no cap and nothing is cut off.

Each delivery carries this body:

{
  "type": "audience_member",
  "audience_id": "0192f3a1-…",
  "audience_name": "Purchasers",
  "global_user_id": "0192f3b0-…",
  "external_ids": {
    "external_id": "0192f3b0-…",
    "crm_client_id": "4821",
    "whmcs_clientid": "4821",
    "email": "ali@example.com"
  }
}

external_ids carries only the keys AdPix actually has for that person. The body is membership only — attribution and order values travel in business-event payloads.

People who leave an audience are not sent a removal message; clearing them on the receiving side is up to you. Your receiver must be idempotent on global_user_id.

Delivery guarantees#

Delivery runs through the transactional outbox — the same path business events take to the CRM — so a receiver that is briefly down does not lose data:

Subject Behaviour
Queue write transactional; the push succeeds once the rows are queued
Drain cycle every two seconds, up to fifty ready rows per pass
Success any response under 300
Failure up to twelve attempts, exponential backoff capped at one hour
After the last attempt the row moves to the dead-letter queue and is never sent again
A stuck row a delivery left in flight for more than twenty minutes becomes retryable

Delivery is at least once: a row is never queued twice, but if your receiver answers 200 and the connection drops before the answer arrives, the same row is sent again. Each request times out after fifteen seconds.

Deleting a destination clears its queue

Deleting a destination also deletes its pending deliveries. To pause, switch the destination off instead.

Deleting an audience#

Delete removes the audience and its membership. It disappears from comparisons and overlap straight away. Whatever was already delivered stays in your CRM — AdPix sends no removal message.

Frequently asked questions#

Why is the estimate in the builder the same number as the saved audience?

Because both run the same query. The live estimate, the suggestions and the saved audience's refresh share one definition compiler, so an estimate is never an approximation of the saved size — it is the saved size, computed before you save.

What is the difference between Users and Devices?

Users counts people: a signed-in person who used a phone and a laptop is one user. Devices counts browsers and apps (distinct device IDs), which is what most reports call users. An audience shows both; Users is the headline.

Can an anonymous visitor be a member?

Yes — membership is computed over every visitor who matches. Only the push to a destination is restricted: anonymous visitors never leave AdPix; a destination receives identified members only (a sign-in, an email, a phone number or a CRM customer ID).

How fresh is membership?

Saving an audience computes it straight away. After that AdPix recomputes it on a schedule — every 15 minutes by default, up to once a day — and you can select Refresh on an audience at any time.

What happens to my old audiences?

Audiences built with the earlier single-row conditions are upgraded when they are read. A condition that has no exact equivalent (does not contain, ends with, regex, or an unknown field) is not guessed at: the audience is marked Error and names the condition to fix. It never silently becomes everyone.

Build with the APIUnderstand where revenue comes from.
Was this page helpful?