The cards below the chart. Each ranks one dimension by traffic in your selected range.
What is available
| Card | Tabs |
| Geography | Map, Country, Region, City |
| Technology | Browser, OS, Device |
| Sources | Channel, Referrer, Campaign, Keyword |
| Pages | Hostname, Page, Entry page, Exit link, Files |
| Goals | Goals, Funnel |
| AI | Crawlers, AI pages — with four cards above them picking the category |
Drilling down
Hover any row and click the funnel at its end — the whole dashboard filters to it. Every card, every tile, every chart. (Clicking the row itself pins its tooltip.)
Filter a second row in a different card and the filters combine — country
India and browser Chrome gives you Indian Chrome traffic. Two rows in
the same card replace rather than combine; a visit cannot be from two countries.
The Filters button above the tiles shows a count when any are active. Open it to see what is applied, remove one, or clear them all.
Filters and the date range are independent — changing one keeps the other.
Revenue in a breakdown
If you have connected Stripe, hovering a row shows what it earned alongside its visitors — so the channel, campaign, country, referrer, browser and device lists all answer which of these brings the money, not just which brings the traffic.
They are rarely the same answer. The channel sending the most visitors is often not the one paying for itself.
The world map does the same: hover a country for its visitors and its revenue. The map's shading stays keyed to visitors, because one large order should not repaint a country the product is barely used in.
A row with no payments shows no amount at all, rather than $0. On a site
that never set up revenue tracking every row would otherwise read zero, which
hides the difference between "measured, and it was nothing" and "not measured".
The Pages list is the exception, and deliberately: a payment is recorded where the checkout completed, so crediting pages would put everything on one row and nothing anywhere else. True, and useless.
Entry pages carry it instead, which is the more useful question anyway —
not where someone paid, but which page brought them in. On this site
/tools/youtube-title-checker earned $665 across six payments while the home
page earned $87, and no page-level report would have shown that.
Filters move the revenue too
Apply a filter and the Revenue tile follows it. Filter to Germany and you see what German visitors paid; filter to a goal and you see what the people who completed it went on to spend.
That last one is the useful pairing. Track the form submission as a goal, click it, and the tile answers what did the people who filled this in actually buy — without needing to send us any figures yourself, since Stripe already reported them.
Payments with no visitor attached drop out under a filter. If nothing links a payment to a visit, it has no country and no channel either, so counting it under "Germany" would be inventing an answer. With no filter applied it still counts toward the total, on its own "unattributed" line.
Payments imported from Stripe when you first connected are the largest group of these, and permanently so: they were taken before anything was tracking, so there is no visit to link them to. They count in your totals and your revenue chart, and they stay out of these lists.
Imported Google Analytics history in a breakdown
If you have imported Google Analytics history and the selected range reaches back before your first event here, the lists gain Google's rows for those days. A row that came from Google, or was summed with Google's figure, carries a small Google Analytics icon at the end of its label. Hover it: below the row's own numbers, behind a separator, a Google Analytics section lists Google's views and visitors and the part measured here, so the two counting systems are never folded into one number silently.
Pick a range that starts after your first event and none of this appears.
What you can filter by
Path, page pattern, browser, operating system, device, country, region, city,
referrer, channel, utm_source, utm_medium, utm_campaign, utm_term, and
crawler type.
Equality only. There is no "is not", no "contains" and no numeric comparison.
The one exception is the page pattern, which accepts * as a wildcard, so
/blog/* filters to everything under /blog/.
How many rows you see
Each card shows a top-N. Cards are display limits, not data limits: the rows below the cut still exist and still count toward your totals — they are just not listed.
Top pages shows the top 10; the rest show 20.
Countries is the exception — it fetches up to 250, because the world map needs every country it can colour. Truncating to 20 would leave the long tail grey, which reads as "no traffic" rather than "not in the top 20".
Per-card notes
Top pages
Ranked by views, keyed by path only — no hostname. So /pricing on your
marketing site and /pricing on your docs subdomain are one row. See
Subdomains.
Paths longer than 500 characters are truncated at the tail. The view is still recorded.
Referrers
Where a visit came from, by hostname. Traffic from your own hostnames is excluded — it shows as Direct instead — provided you have listed them under Self hosts in the site's settings. See Channels.
Browsers
Grouped on the raw browser name as reported. If you are comparing against another analytics tool, note that some of them fold Mobile Safari into Safari and we do not. That alone can account for a visible gap.
Campaigns and Keywords
Built from the UTM parameters on your inbound links. Campaigns groups by the UTM
combination; Keywords ranks utm_term.
If you are not tagging your links, both cards are empty and that is expected.
Regions and Cities
Derived from the visitor's IP address at the moment the request arrives, then the IP is discarded. Accuracy is what IP geolocation gives you: countries are close to reliable, cities are approximate, and a VPN reports wherever it exits.
Bots and breakdowns
With the default Hide bots filter on, every breakdown shows humans only. Turn it off and crawler traffic folds into all of them — you will see a spike in "other" browsers and in whichever countries the crawlers run from.
The AI card is the exception: it always shows crawler data regardless of the filter, since that is its entire purpose. See AI visibility.