AUDIENCE & BREAKDOWNS
Know who shops here.
And who gets stuck.
The same anonymous context travels with every session, so a pattern you notice in your audience can be followed into an issue, a journey step, a page or a Core Web Vital.
Seven ways to read your audience.
Switch the tile. Each row counts sessions once, shows how they converted and opens the matching sessions.
OVERVIEW · AUDIENCE
Who were this month’s shoppers?
SEGMENT THAT CONVERTS WORST
Shoppers on 3G convert 60% less.
1.4% against 3.5% on 4G · both sides 200+ sessions · gap is statistically clear.
Each session counted once. Rows open the matching sessions. Bots, crawlers and headless browsers are excluded.
Start with who arrived.
Overview ranks landing pages, channels, campaigns, countries, devices, browsers and operating systems by sessions in the selected window, each session counted once. Every row opens those sessions, so “paid social on iOS” is one click from their timelines. Bots, crawlers and headless browsers are never in the count.
Follow a segment into the journeyLet the gap speak only when it is real.
Overview compares purchase conversion by country, connection type and device-memory band, and names the segment that converts worst only when it and the rest each have 200 or more sessions, the gap is at least 25% and a two-proportion test separates it from noise. Until then the card says it is collecting.
See how impact is measuredSplit every question the same way.
An issue breaks down by eleven dimensions plus in-app browser, offline and extension shares. A journey step compares each device, browser and channel’s share among drop-offs with its share at entry. Pages compare segments against the page’s own baseline, and Core Web Vitals split by browser, OS, viewport, connection and device memory.
Open an issue breakdownA LITTLE MORE DETAIL
Good questions.
Useful answers.
Which breakdowns are available?
Overview: landing page, channel, campaign, country, device, browser and OS. Issues: browser, device, OS, viewport, country, connection, device memory, page group, URL, channel and campaign, plus in-app browser, offline and extension shares. Journeys: device, browser and channel at each step. Performance: browser, OS, viewport, connection and device memory.
Why do some sessions show Unknown connection or memory?
Only Chromium browsers report connection type and device memory. Safari and Firefox sessions appear as Unknown in those two breakdowns. That is a real share of your traffic, not missing data.
Does it identify individual shoppers?
No. Segments come from anonymous session context: the landing URL, referrer, user agent and the country from the network edge. No fingerprinting, no input values and no cross-session profile.
Is a large segment the cause of a problem?
Not by itself. A segment that is 70% of an issue may simply be 70% of your traffic. Compare drop-off share with entry share, or a page segment with the page’s baseline, then confirm in a session or replay.
CONNECTED PRODUCT WORKFLOWS
Follow the next connection.
An issue, a journey, a page or a release. Each view gives you a way into the next.SEE IT ON YOUR STORE
Bring a real problem to the demo.
Bring the journey you want to improve and the person who ships your changes. We’ll look at your first evidence together.
Book a demo Estimate your price and contact us · Guided setup