Page Groups Ranked
The Pages card on the board ranks the path groups on your site by page view count for the selected date range. Each row is a two-segment URL path class, not a full URL, so pages with different query strings or ID suffixes merge into readable groups.
What a path group is
When a beacon arrives, StatelessID extracts the URL path and reduces it to at most the first two segments. The query string is stripped. The fragment is stripped. Only the path portion of the URL counts, and only the first two directories of that path. The path /blog/how-to-use-widgets becomes /blog/how-to-use-widgets unchanged (two segments). The path /shop/product/12345/reviews becomes /shop/product — the third and fourth segments are dropped.
The root path / counts as its own group. The path /about counts as its own group. Paths that do not conform to the two-letter-and-number segment rules, or that contain spaces, special characters, or query strings, are rejected at collection time and do not appear on the board at all.
This grouping approach is intentional. On an e-commerce site with 50,000 product pages, showing each product's individual URL would create an unreadable table. Grouping at two segments collapses /shop/product/1, /shop/product/2, and /shop/product/3 into a single /shop/product row with the combined view count of all three.
Reading the ranked list
The Pages card shows the top page groups by visit count for the selected range, with a horizontal bar proportional to each group's share of the total page views. The bar length is relative to the top-ranked group — the top row always has a full-width bar, and every other row is proportional to it.
The compact view in the main board shows the top four groups. The full list is available in the page-groups section of the collapsible drawer, where you can also assign a monetary value to each group. The drawer list includes all groups that meet the privacy floor, not just the top four.
Rows below the privacy floor of five views are folded into an Other entry. Other appears at the bottom of the list and represents the combined count of all groups that were too small to name individually in the selected range. A large Other count relative to the named rows means your traffic is spread across many low-traffic pages rather than concentrated on a few.
Page values and assigned amounts
In the collapsible drawer, each named page group has a form where you can assign a monetary amount and a direction — add or subtract. When you assign an amount, the board calculates a running total by multiplying the page view count for that group by the assigned amount and summing across all assigned groups for the selected range.
The total is displayed as a single number at the top of the page-groups section: "Assigned total for this range: $X.XX." This total is not a payment or an invoice. It is a rough revenue-attribution estimate you can use to understand which pages are likely driving or losing value relative to their traffic.
Assigned amounts persist across range changes. If you assign $1.00 to /pricing for the current week and then switch to last 30 days, the total recalculates using the /pricing view count for the last 30 days. You can clear an assignment at any time using the Clear button next to the row.
Path group limits and the two-segment rule
Paths are accepted only if every segment consists of letters, digits, dots, underscores, or hyphens, and each segment is no longer than 48 characters. A path like /news/2026-08-31/breaking-story is accepted as /news/2026-08-31. A path like /api/v1/users/profile/edit is accepted as /api/v1. A path containing a space or an @ symbol is rejected entirely.
If your site uses path-based IDs — for example /users/12345 — the group /users will accumulate all user profile views under one row. If you need to track individual users separately, that requires joining on identity, which StatelessID does not do. The board shows aggregate counts for the group, not per-ID breakdowns.
Filtering the board by page group
There is no per-page filter on the current board. The range selector narrows the time window; the event-type selector narrows the event type. But you cannot tell the board to show only data from a specific page group. The Pages card ranks all groups together. To focus on a specific section of your site, use the CSV export and filter the exported file by the path group column.
If you need to compare two date ranges for a specific page group, use the period-compare feature in the collapsible drawer combined with the CSV export. The period-compare tile shows the cycle totals side by side, and the CSV will include the path-group breakdown that you can then filter offline.
Troubleshooting
If a page you know exists on your site is not showing up in the Pages card, confirm that the path has at least five views in the selected range and that the URL does not contain a query string. Also confirm that the URL path conforms to the two-segment, alphanumeric-only rule — paths with special characters are rejected silently.
If the Pages card shows only Other with no named rows, widen the date range. The privacy floor is five views per group per range, so a narrow range on a low-traffic site will show only Other.