Key takeaways
- In AdPix, the working tool for segmentation is Audiences: rules with user, session or event scope, include groups joined with OR, sequences, exclusions and a look-back of 1 to 540 days.
- A saved audience can be added as a comparison on most reports, intersected with two others in the overlap view, or pushed to a webhook, which receives identified members only.
- The separate Segments page is still marked Coming soon in the AdPix docs: AND-only conditions, no editing, and its segments apply only inside explorations.
- Audiences, segment overlap and custom reports (explorations) are included from the Starter plan; built-in and custom comparisons on standard reports are not plan-gated.
- Scope changes the answer: a user-scoped 'did purchase' keeps everything buyers did, while an event-scoped one keeps only the purchases.
AdPix segments answer one question: how does a specific group of people behave compared with everyone else? In AdPix you build that group as an audience, a saved set of rules such as “added to cart, then did not purchase within 3 days”, and then use it in three places: as a comparison on most reports, in an overlap view against two other audiences, or as a list pushed to a webhook. Audiences, segment overlap and custom reports are included from the Starter plan. This page covers how the rules work, how scope changes the numbers, two worked examples, and where the feature stops.
Segment is a subset of your analytics data, defined by conditions on users, sessions or events, that you analyze separately or compare against the whole.
What question do AdPix segments and audiences answer?
AdPix audiences answer “who exactly are these people, and how do they differ?” A report tells you that 3% of visitors bought. An audience tells you whether mobile visitors from paid search buy at 1% or 5%, whether your cart abandoners are mostly first-time visitors, and whether two paid channels are paying twice for the same people.
The tool you pick depends on the question:
| Your question | AdPix tool | Plan |
|---|---|---|
| How does this group compare with all users on a standard report? | Comparison bar with a saved audience | Starter and up (built-in and custom comparisons need no plan) |
| Do two or three groups contain the same people? | Audience overlap | Starter and up |
| Which cities, devices or campaigns stand out for a group I filter to? | Explorations (custom reports) with a segment | Starter and up |
| Can I send this group to my CRM or SMS tool? | Audience destination (webhook or WHMCS) | Starter and up |
| Where do people drop on a fixed path? | AdPix conversion funnel | Every plan, including Free |
There is a naming wrinkle worth clearing up first. AdPix has a separate page called Segments, and the AdPix docs on segments say plainly that it is parked under Coming soon. The working, fuller tool is Audiences, under Activate in the sidebar. When this page says “segment” in the AdPix context, it means an audience unless it names the Segments page.
Who are AdPix segments and audiences for?
They suit anyone whose next decision depends on a group rather than on the site as a whole. Three roles get the most out of them:
- Store owners and e-commerce managers who want to see cart abandoners, repeat buyers or high-value customers as a group and follow up with them.
- Performance marketers who need to know whether a channel’s traffic behaves differently once it lands, or whether two campaigns reach the same people.
- Lead-generation and SaaS teams who want to separate people who requested a demo from people who only read the pricing page, and push the first group to sales.
Audiences work best when you already send the events your rules depend on. A rule on purchase or generate_lead can only count what the tag collects, so if your event tracking is thin, fix that first.
How does segmentation work in analytics tools generally?
Analytics tools usually split segmentation along one decision: scope. Google’s segment builder documentation describes three scopes, and the difference is easiest to see with one person. A visitor browses on day one without buying and returns on day two to buy. A user segment for “made a purchase” returns everything that person did on both days. A session segment returns only the day-two session. An event segment returns only the purchase event.
Pick the wrong scope and the numbers still look plausible, which is why this matters. “Pages viewed by buyers” needs user scope. “Pages viewed in buying sessions” needs session scope. “Revenue from orders over $100” needs event scope.
Two other choices separate tools:
- Filter versus saved group. In GA4, segments live only inside Explore and are applied to explorations, while audiences are saved groups that GA4 fills as people meet the conditions (Google Analytics Help: segment builder).
- Forward-only versus historical. GA4 audiences accumulate users who meet the conditions from the point of creation onward (Google Analytics Help: audiences). A new GA4 audience starts nearly empty for analysis.
How do audiences work in AdPix?
An AdPix audience is a named group of people on one website, defined by include rules and exclude rules, whose membership AdPix computes and keeps current. The AdPix audiences documentation describes these building blocks.
Include groups. Each include group holds up to ten conditions, and you choose whether all or any of them must hold. You can add more groups with “or”: a person who satisfies any include group is in. Each group has its own scope, user, session or event, with the same meaning as above.
Condition types. There are five:
| Type | Example | Notes from the docs |
|---|---|---|
| Event | did purchase at least 2 times in the last 30 days |
count of 0 means “did not do it”; up to three parameter filters, such as value ≥ 20 |
| Dimension | device category is one of mobile, tablet | channel, source, campaign, country, city, device, page path, custom event parameters and more |
| Sequence | added to cart, then did not purchase within 3 days | 2 to 6 steps within 1 to 90 days; only the last step can be “did not” |
| CRM trait | plan is not one of free | identified people only |
| Audience | is a member of Purchasers | membership of another audience on the same website |
Matching is exact (is one of, is not one of, contains, starts with, greater or less than). There is no regular-expression match, and a dimension name the server does not recognize is rejected with an error rather than silently matching everyone.
Exclusions. A temporary exclusion is checked inside the membership window, so someone who stops matching comes back. A permanent exclusion looks at all history: “ever refunded” removes a person for good.
Membership duration. This is the look-back, from 1 to 540 days with a default of 90. A person needs at least one event in that window. Because AdPix computes membership from events already collected as soon as you save, a new audience is filled from history, not from the day you created it. That is the main practical difference from GA4.
The live estimate. While you edit, a side panel recomputes the audience about half a second after each change and shows its size, its share of all users and its overlap with your ten largest saved audiences. The docs state that the estimate runs the same query as the saved audience, so the number you see before saving is the number you get. After saving, membership refreshes every 15 minutes by default. Each website can hold up to 100 audiences.
Suggested audiences. To save typing, New audience offers ready-made groups sized on your last 28 days: 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.
How do you use an audience in AdPix reports?
You use it in three places: the comparison bar, the overlap view and a destination.
As a comparison. The bar under the date picker splits a report into up to five series: All users plus up to four comparisons. It appears on Home, acquisition, engagement, events, the funnel, e-commerce, attribution, Cost & ROAS and realtime, among others (AdPix docs: comparisons). The counting rule matters. A dimension comparison, such as Mobile traffic, filters events, so one person who used a phone and a laptop appears in both series. An audience comparison keeps people: a Purchasers comparison shows those buyers’ whole activity, not only their purchases. On Cost & ROAS, ad spend is not split, because spend is imported per channel and day; each comparison’s ROAS is its own revenue against the whole spend. Read the ROAS formula guide before you treat that figure as the segment’s true return.
In the overlap view. Pick two or three audiences and AdPix draws a diagram with areas proportional to size, labels every region with an exclusive count, and adds a pairwise table with the shared count, each side’s share and a Jaccard similarity score, shared people divided by people in either (AdPix docs: audience overlap). Any region can be saved as a new audience, such as “in A, not in B”. Overlap counts only members active in the selected date range.
As a destination. Destinations are set up under Admin, Integrations, as a generic webhook or a WHMCS install. Only identified members leave AdPix: people linked to a sign-in, an email, a phone number or a CRM customer ID. The first sync sends every current member, and later syncs send people who joined since. People who leave the audience are not sent a removal message, so the receiving system has to clear them itself. Google Ads and Meta destinations are listed as Soon in the builder.
Two worked examples: a shop and a lead-generation site
A shop recovering carts. This example is hypothetical. A shop builds a user-scoped sequence audience, “add_to_cart, then did not purchase within 3 days”, with a 30-day membership duration. The live estimate shows 1,200 people. The audience page splits users from devices; say 480 of the 1,200 are identified because they entered a mobile number at checkout. Only those 480 can be pushed to the shop’s SMS tool through a webhook.
If a reminder brings back 6% of them at an average order of $40, that is 480 × 0.06 = 28.8, about 29 orders, or roughly 29 × $40 = $1,160 in a month. Whether those orders are extra or would have happened anyway is a separate question; an incrementality test with a holdout group is how you answer it.
A lead-generation site checking channel overlap. Also hypothetical. A B2B site builds two audiences: A, “paid search visitors” (4,000 people), and B, “viewed /pricing” (1,500 people). The overlap view shows 900 people in both.
| Figure | Arithmetic | Result |
|---|---|---|
| Share of A in B | 900 ÷ 4,000 | 22.5% |
| Share of B in A | 900 ÷ 1,500 | 60% |
| Jaccard similarity | 900 ÷ (4,000 + 1,500 − 900) | 19.6% |
Read the two percentages, not the similarity score, to decide containment. Sixty percent of pricing-page viewers came through paid search, so paid search feeds most of the people who reach pricing. Saving the region “in B, not in A”, 600 people, gives a group of organic and direct pricing viewers whose sources are worth checking in the acquisition reports. Clean campaign tags make that check possible; the UTM parameters guide covers the setup.
Which AdPix plan includes segments and audiences?
Audience segments, segment overlap and custom reports are included from the Starter plan, at 499,000 toman a month, and on Pro and AdPix 360 (AdPix pricing). On Free, the Audiences and Reports & Explore pages show an upgrade card instead (AdPix docs: plans and entitlements). Built-in comparisons, such as Mobile traffic or Organic, and custom comparisons on a dimension are not plan-gated, so a Free website can still compare groups on standard reports without saving an audience.
| Plan | Price | What it means for segmentation |
|---|---|---|
| Free | Free | Built-in and custom comparisons on standard reports, funnels, acquisition and e-commerce reports; 100,000 page views a month for each website |
| Starter | 499,000 toman a month | Audiences, audience overlap, explorations (custom reports), destinations, API access; 1 million page views a month |
| Pro | 2,990,000 toman a month | Everything in Starter, plus MMM, lift tests and fraud blocking; 10 million page views a month |
| AdPix 360 | By contract | Scale, access control, deployment options and support |
Roles matter too. Creating, editing and pushing audiences needs the marketer role or higher; creating explorations and segments needs analyst or higher. Reports in every plan are unsampled, so a small audience is counted from all of its events rather than estimated, which is the problem GA4 data sampling creates in large explorations.
AdPix is a web analytics platform that replaces Google Analytics 4: realtime, acquisition, engagement, conversion and e-commerce reports, plus attribution, lift testing and marketing mix modelling, with no data sampling and a free plan. The AdPix features overview shows where audiences sit among the other reports.
How do you build your first audience in AdPix?
Start from a suggestion, not a blank builder:
- Open Activate, Audiences, and select New audience.
- Pick a suggested audience, such as Cart abandoners. If it shows no size, the docs say it names the event your website has not recorded in the last 28 days; fix tracking first.
- Open it as a template, adjust the window or add an exclusion, and watch the live estimate.
- Save it. Membership is computed straight away.
- Add it as a comparison on Traffic acquisition and on E-commerce, and compare its channel mix and order value with All users.
- Build a second audience, such as Purchasers, and open the overlap view to see how much the two share.
What are the limits, and when should you use something else?
These are the cases where AdPix audiences are the wrong tool or need care:
- You want the Segments page. It is still marked Coming soon: conditions are AND only, a saved segment cannot be edited and shows no size, a condition with an empty value is dropped silently, and a segment applies only inside the exploration builder (AdPix docs: segments). Build the group as an audience instead.
- Anonymous visitors in a destination. Membership includes anonymous visitors, but a push sends identified members only. An audience of 5,000 can deliver a few hundred contacts.
- Ad platform remarketing. Google Ads and Meta destinations are not available yet. If your goal is a remarketing list today, use each platform’s own pixel audiences.
- Exploration caps. Explorations take three dimensions and four metrics, sort by the first metric, and pivot only the top six values of a dimension (AdPix docs: explorations).
- Users versus devices. An audience headline counts people, while reports count devices, so an audience of 120 users can show 140 devices on a report comparison.
- Cohorts and predictions. Cohort retention is marked Coming soon in the docs, and predictive audiences are marked Soon. For retention questions, use the reasoning in the customer lifetime value guide with purchase-based audiences.
- Shared links and scheduled emails. Comparisons are not yet frozen into shared report links, exports or scheduled emails, which show All users only.
The fastest next step is the cart abandoner audience: save it, add it as a comparison on Traffic acquisition, and look for the channel whose visitors abandon most. Then check which of them you could reach, because a group you cannot contact is an insight, not a campaign. The first-party data guide explains how to collect the sign-ins and phone numbers that turn one into the other.
Measure your site with AdPix today
The free plan covers 100,000 page views a month for each website, no credit card. Setup takes under five minutes.
Frequently asked questions
What is the difference between a segment and an audience in AdPix?
In AdPix, an audience is a saved, rule-based group of people whose membership is kept up to date and can be used as a report comparison, in the overlap view or pushed to a webhook. A segment, from the separate Segments page that is still marked Coming soon, is a filter used only inside the exploration builder.
Which AdPix plan includes segments and audiences?
Audience segments, segment overlap and custom reports are included from the AdPix Starter plan, at 499,000 toman a month, and on Pro and AdPix 360. They are not on the Free plan, where a website sees an upgrade card instead.
Can AdPix audiences use OR logic?
Yes. Each include group holds up to ten conditions that must all or any hold, and several include groups are joined with OR. The separate Segments page combines conditions with AND only.
Are AdPix audiences filled from past data?
Yes. AdPix computes membership as soon as an audience is saved, using the events already collected inside the membership duration of 1 to 540 days. Google Analytics 4 audiences, by contrast, accumulate users from the moment they are created.
Can I send an AdPix audience to Google Ads or Meta?
Not yet. The audience builder lists Google Ads and Meta as Soon. Today an audience can be pushed to a generic webhook or a WHMCS install, and only identified members, such as signed-in users or people with a known email or phone number, are sent.
Sources and methodology
Screen names, limits, scopes, condition types and delivery rules for AdPix audiences, segments, overlap, explorations and comparisons come from the official AdPix documentation at docs.adpix.io, read on 21 November 2026 and linked in each section. Plan placement and prices come from adpix.io/pricing (read on 13 November 2026). GA4 behavior comes from Google's Analytics Help pages on the segment builder, audiences and comparisons, read on 21 November 2026. The shop, the lead-generation site and every count, rate and order value in the worked examples are hypothetical and chosen to keep the arithmetic easy to follow.
- AdPix Docs: Audiences and destinations
- AdPix Docs: Audience overlap
- AdPix Docs: Segments
- AdPix Docs: Explorations
- AdPix Docs: Comparisons
- AdPix Docs: Plans and entitlements
- Google Analytics Help: Segment builder
- Google Analytics Help: Create, edit, and archive audiences
- Google Analytics Help: Apply comparisons to reports
This article was drafted with AI assistance and reviewed by the AdPix team before publishing. Editorial policy