Feature request: Treat i18n path segments as a separate dimension from page paths

[bryanrsmith]

My site uses next.js's i18n support in the sub-path routing configuration. The locale path segment is causing the new Audiences feature to treat different locales as different pages, which isn't very helpful.

My top pages looks like this:

/compare
/en/compare
/
/en-GB/compare
/en
/de-DE/compare
/en-GB
/about
/de-DE
/en/about

It'd be great to have some way to collapse these locales into a single entry in Audiences. e.g.:

/compare
/
/about

As a bonus, if the locale could be treated as a separate dimension then it would be cool to have a pane with a breakdown of visitors by locale.

---

I'm excited to see Vercel investing in this area! Thanks!

[tobiaslins]

Hey @bryanrsmith,
Thanks for your feedback!
We already have a ticket in the pipeline that will handle all dynamic paths (including i18n).
For example:
Grouping /users/[id] or /[lang]/about as you mentioned!

We can't give any timeline on that yet!