scroll depth #573
scroll depth #573
Conversation
There was a problem hiding this comment.
Fantastic job on this PR, @metmarkosaric and @Hricha-Shandily! 🥳
A couple of suggestions with more technical context inline. Feel free to adjust the copies.
| @@ -87,6 +87,10 @@ You can click on any source to drill-down and view the individual pages linking | |||
|
|
|||
| Shows the devices used by your visitors. Devices are categorized into desktop, mobile or tablet. This is derived from the User-Agent HTTP header. The full User-Agent is discarded. Metrics are shown as the total number of unique visitors and as a percentage of all visitors. | |||
|
|
|||
| ## Scroll Depth | |||
|
|
|||
| Measures how far visitors scroll down a webpage. It represents the percentage of a page’s total height that visitors have reached on average. You can learn how we calculate it [here](http://plausible.io/docs/scroll-depth).``` | |||
There was a problem hiding this comment.
I think the metric definitions page should also give a pretty accurate description of how things work technically. Reading this paragraph, I get the impression that clicking this link will take me to the technical description.
Proposal: lets include something like this on the /docs/scroll-depth page:
How is scroll depth tracked in Plausible?
When a user first opens the page, a percentage of it is visible already. That height visible to the user, divided by the total height of the page is the initial scroll depth percentage. We then keep track of the maximum depth as the user scrolls, and reaching to the very bottom, the percentage would become 100%.
Described above is only a single pageview. What if a user visits the same page multiple times during their visit, scrolling to different depths each time? In that case, the scroll depth of that particular page for that visit is simply the maximum up to which they reached across all pageviews on that page.
Finally, the average metric that you can see in your dashboard is simply an average of all visits.
There was a problem hiding this comment.
This is good info but I have noticed we don't generally include much about technical details regarding any feature in the documentation. I guess this is to keep the doc as simplified to comprehend as possible and not include info that has potential to confuse the reader (no matter how simple we make it). Is that so, @metmarkosaric ?
There was a problem hiding this comment.
@Hricha-Shandily yeah, that's correct. in general, we tend to keep more (technical) details out of the docs by default. we do sometimes surface some details (see for instance this on how locations work: https://plausible.io/docs/countries#how-location-reporting-works) but this is more if we notice that something is unclear and/or people are asking. so i say we keep this info in mind and add it to the docs at a later stage if it turns out that simplified docs are not clear enough
|
|
||
| Plausible tracks scrolling at all percentages (1% to 100%), unlike many other tools that limit tracking to specific points such as 25%, 50%, and 75%. If you also want to track a specific scroll depth threshold for some of your pages, you can set up scroll depth goals. | ||
|
|
||
| ## Scroll Depth goals |
There was a problem hiding this comment.
There are two limitations that I think we should mention in this section.
- Number of conversions might appear lower than it really is
Our tracking script captures scroll depth at the moment when the visitor leaves a page. But it can't always do so due to browser limitations. E.g. sometimes, browsers won’t detect when a user leaves if they switch apps or move the browser to another screen. While we use best practices to maximize accuracy, some of these events will always be missed.
- Number of total conversions is not available for Scroll Depth goals
While for pageview and custom event goals we can easily tell how many events there were in total, we cannot say the same for Scroll Depth goals as scrolling is an action that gets measured continuously during a pageview.
There was a problem hiding this comment.
Thanks Robert!
I have added the second point, @metmarkosaric . If it looks good (you should be able to see it below), I will commit the suggestion.
For the accuracy part (first point), I am thinking it is something we don't need to say as it could overcomplicate and unnecessarily raise questions about our accuracy and increase the support volume as well.
| You can for instance group all of your blog posts by using `/blog*` (if your blog subdirectory is named `blog`) or your Woocommerce checkout pages by using `/checkout/order-received/*`. | ||
|
|
||
| Next, click on the "**Add goal**" button to return to the goals page. When you navigate back to your Plausible Analytics dashboard, you should see the number of visitors who reached the particular scroll depth on the specified pages. Goal conversions are listed at the bottom of the dashboard. | ||
|
|
There was a problem hiding this comment.
| Scroll Depth goals only display the "Uniques" and "CR (conversion rate)" metrics, and not the "Total" metric like the pageview goals and custom event goals do. This is because scrolling is an action that gets measured continuously during a pageview and it's not possible to count the total number of "scroll depth events" that occurred. | |
No description provided.