[Feature Request] 'Path' level Data from CrUX, like origin but specific to that path

[Dave Smart]

No idea how feasible this would be with how the data is stored, but it would be great if in addition to origin and url specific data, there could be a third, almost in between level of path,

i.e. for the path of https://example.com/foo

You'd get the aggregate for:
 https://example.com/foo
 https://example.com/foo/bar
 https://example.com/foo/bar/baz

and so on.

Many sites are structured with different types of content on different paths, an example might be a Shopify site that has product and categories on /collections/, informational content on /blog  and so on.

I think that would help developers and site owners understand how different types of URLs on their site are performing, and almost allow a 'group' view à la search console

Even bigger bonus points if you could specify wildcards, so something like https:///collections/*/products/
Could give you data on how your product details pages were performing on a Shopify site for example.

[Barry Pollard]

Hi Dave,

We don't have plans to add that level of detail to CrUX, and in many cases it would likely only be a partially complete story as many paths would fail to meet the minimum privacy thresholds for many paths. We would suggest using a RUM solution to allow that level of granularity. CrUX, as a public dataset, is more intended as a high-level indication of performance than a fully queryable, segmentable solution such as that that can be offered by RUM.

The  nearest thing that is available now is the Page Grouping in Google Search Console, but I know that is not quite in the same level of detail as you're asking for (perhaps for the same reasons as above?), and is only available to verified owners of that domain (again, perhaps for that reason). As that's managed by the separate Search team we in the CrUX team don't have any more visibility into that.

Thanks,

Barry

[Dave Smart]

Hey Barry.

Definitely hear you on RUM being the way forward for most folks interested in this level of detail. Would have been nice to be able to plugin in and get going, but yeah, I can see how the privacy aspect c omes in to play.

Thanks for the reply!