Discussion: omit query string to stop polluting path table?

[benvinegar]

This is getting pretty irritating:

I think there are cases where you want query string, but you certainly don't want to see things like utm_params.

Options as I see it:

1. Strip the query string (distinct paths only)
2. Remove (and potentially store) known params like utm_params, ref, etc. from query string
3. Do nothing

What would people like to see done here?

[drewrawitz]

I think the query parameters are useful data, but I agree that it makes the UI a tad messy. What if you show the distinct paths only, but have the ability to expand a top-level path to reveal the breakdown based on query parameter variations?

Here's a super quick and dirty mockup that I just did in the dev tools:

And expanded:

Ignore the last link, that would be grouped under the / path, but I was just focused on the /dashboard in this example!

[benvinegar]

I think because comparable products strip the query string, and because Counterscale promotes itself as being privacy-sensitive, it's worth doing the same (removed in c6493a5).