Most sites are built from a handful of page types: blog posts, product pages, search results, a checkout flow. Each type usually shares a layout and behaves similarly, but lives under many different URLs.
Page Groupings let you label a set of URLs with a pattern so you can measure them together. Instead of reading one row per URL, you see how an entire type of page performs, which makes trends and regressions far easier to spot.
Creating a Blog Posts grouping with the pattern /blog/* lets you see how every blog post performs as a whole, rather than scanning hundreds of individual URLs.
Create a page grouping#
Page groupings are managed per Site. To create one:
- Navigate to your Site → Real User Monitoring → Settings → Page Groupings.
- Click Add Page Grouping.
- Enter a Name (for example,
Blog Posts). This is the label shown across RUM reports. - Enter a Pattern (for example,
/blog/*). This is the URL pattern that decides which paths belong to the grouping. A pattern must start with/and contain at least one*. See Pattern syntax below. - Click Save.
New and changed groupings are applied to your existing RUM data, not just to sessions collected from then on. After you save, reports update once the data has been reprocessed.
Pattern syntax#
A pattern is a URL path with one or more wildcards, matched against the page path (the part after the domain, starting with /). Every pattern must start with / and contain at least one *.
Wildcards#
| Wildcard | Matches | Example |
|---|---|---|
* | Any text within a single path segment. It does not cross a /. | /blog/* matches /blog/hello-world but not /blog/2026/hello-world. |
** | Any text across multiple path segments, including /. | /docs** matches /docs, /docs/page, and /docs/api/v1. |
Use * to capture the direct children of a path, and ** to capture a section and everything nested beneath it.
Examples#
| Pattern | Matches | Does not match |
|---|---|---|
/products/* | /products/shoes, /products/hats | /products, /products/shoes/reviews |
/docs** | /docs, /docs/api/v1 | /help |
/blog/*/comments | /blog/hello-world/comments | /blog/hello-world |
A wildcard can sit anywhere after the leading /, including in the middle of the path (/blog/*/post) or at the end (/docs**).
How a path is matched to a grouping#
Each page path belongs to at most one grouping. When a path could match more than one pattern, Calibre assigns it to the most specific grouping:
- The pattern with the most path segments wins.
- If two patterns have the same number of segments, the one with fewer wildcards wins.
For example, given /blog/** and /blog/*/comments, the path /blog/hello-world/comments is assigned to /blog/*/comments because it is the more specific pattern.
Paths that match no grouping pattern are reported as Ungrouped, so no traffic is ever hidden. The Ungrouped row is a useful prompt: a large Ungrouped session count often means a common page type is missing a grouping.
Edit or delete a grouping#
From Settings → Page Groupings, use Edit to rename a grouping or change its pattern, or Delete to remove it. Editing a pattern re-evaluates which paths belong to the grouping across your existing data.
Use page groupings across reports#
Once a grouping exists, it is available throughout RUM:
- Pages report: switch the By Path / By Page Grouping toggle to By Page Grouping to see one row per grouping, ranked by sessions or any metric. This is the fastest way to compare how your page types perform against each other.
- Filtering: filter any RUM report to a single grouping using the Page Grouping dimension, the same way you would filter by path, device, or country. See filtering RUM reports.
- Metric reports: on individual metric pages (such as Largest Contentful Paint), segment the chart by page grouping to compare a metric across your page types over time.
- Audience report: the UX Rating breakdown can be viewed by page grouping, surfacing which page types deliver the best and worst experiences.
Filtering by path is best for finding the single best or worst performing URL. Grouping brings the attention up a level, to the page types worth investing in, such as landing pages, the checkout flow, blog posts, or documentation.