3 ms·

General information. How many views/visitors over time, referrers, etc. I did try to click on the top page lists, but those weren’t links. I found "Add segment

General information. How many views/visitors over time, referrers, etc. I did try to click on the top page lists, but those weren’t links. I found "Add segment" eventually, but at least on the demo page it’s not working (for the pages I tried, eventually I found a page with stats), and the interface is atrocious [0] for finding anything and breaks the site [1]. Our website is not posting articles to get people to buy other stuff, but the actual main part of the website (articles, and free or paid product tests; money is made both by selling tests and ads, with the ads not just being generic but specifically bought by companies with often contextual targeting). So my boss usually wants to know what articles do well (and not just from SE’s, we have a lot of repeat visitors), how soon interest drops, etc. [0]: https://i.imgur.com/Buf0Vgd.png https://i.imgur.com/Buf0Vgd.png [1]: https://i.imgur.com/wIO0d2B.png https://i.imgur.com/wIO0d2B.png

XCSme 5y ago
Thanks for the feedback! I will add the per-page stats to the Roadmap, as I think it's a useful feature. I agree, the UI can be greatly improved, and it is something that I will be working on soon, especially making sure all the edge-cases are covered. Regarding the screenshots, the long page-name indeed breaks the UI, but normally you wouldn't search for a specific page including all the query parameters, you would add something like "/pricing*" (so it matches all visitors that visited the pricing page, regardless of the query parameters). I am still not sure whether I should separate query parameters from URL path, I did consider it but many pages use query parameters to display a different page/content (e.g. /article?id=5, where changing the id of the article leads to a completely different page, maybe I could by default exclude all query parameters and then have the option to keep custom an allow-list).
XCSme 5y ago
Could you list a few of the per-page stats that you would want to see? I can only think of time-spent, which I think I could simply display in the top pages list. You can already see sessions count for a specific page using the current segment feature, just add that page name to a new segment, and you can see the count of sessions that saw that page and the referrer (for that specific visitor though, not necessarily that specific page).

XCSme 5y ago

Thanks for the feedback! I will add the per-page stats to the Roadmap, as I think it's a useful feature. I agree, the UI can be greatly improved, and it is something that I will be working on soon, especially making sure all the edge-cases are covered. Regarding the screenshots, the long page-name indeed breaks the UI, but normally you wouldn't search for a specific page including all the query parameters, you would add something like "/pricing*" (so it matches all visitors that visited the pricing page, regardless of the query parameters). I am still not sure whether I should separate query parameters from URL path, I did consider it but many pages use query parameters to display a different page/content (e.g. /article?id=5, where changing the id of the article leads to a completely different page, maybe I could by default exclude all query parameters and then have the option to keep custom an allow-list).

XCSme 5y ago

Could you list a few of the per-page stats that you would want to see? I can only think of time-spent, which I think I could simply display in the top pages list. You can already see sessions count for a specific page using the current segment feature, just add that page name to a new segment, and you can see the count of sessions that saw that page and the referrer (for that specific visitor though, not necessarily that specific page).