Need to track the scroll depth.
More particularly, we would like to know at which part of the scrollytelling the visitors currently are and how much time he/she spents at any particular part.
Ultimately, we want to understand the behavior of the users of this page.
Do you have any suggestions what events we could implement and what would make sense to track in order to fulfill the needs?
Solved! Go to Solution.
Just be aware that a solution that fires an Adobe Tracking call with scrolling will increase your server call usage significantly. While this will work, you should be sure that your current contract level can support the additional calls so that you don't end up with massive overage charges a the end of your billing cycle.
@kamlesh-maddheshiya You can use getPercentPageViewed, The getPercentPageViewed plug-in measures a visitor’s scroll activity to see how much of a page they view before moving on to another page.
Here is the documentation for your reference
My approach is tracking with the 'previous page', mostly due to the cost concern as mentioned by @Jennifer_Dungan. There are multiple page-based metrics I wish to track which could only be available after the page loaded and the initial page view beacon is already gone, such as the page loading speed and the max. scrolling depth.
I don't want to trigger additional tracking upon those events as they will increase the server calls out of control. So I still have rules on those evens but getting the data I wanted and storing them as a session item on the browser together with the name of the current page. Then user navigated to the next page, the page view tracking rule also checks the existence of those 'previous page' data and sends them to Adobe together with the page view.
There are two issues with this approach:
1. we can't track the same on the last page of the visit, as there is no next page to send the data.
2. users need to be educated to use the 'previous page' set of evars and events when doing the report.
Yes, if you are want to use Adobe for this type of tracking, that's the best way to handle this so that you don't increase costs.
Unfortunately, this could cause challenges with the part of your reqs "how much time he/she spends at any particular part" as this falls into a in-depth analysis, which is tough to achieve with a "send all data on the next page"
This is definitely something that is tracked better with a "heartbeat" system over something like Adobe....
However, one thing you could consider is collecting scroll data into your own DB (along with some key data for stitching taken from your Adobe Data) and import it into Adobe? I've never tried this, but it might give the granularity needed, but be available in your Adobe System?
Here is an article about importing GA data (I know you won't be using GA for this), but step 4 (importing) should work for any data source: https://www.fullstackanalyst.io/blog/adobe-analytics/import-google-analytics-data-into-adobe-analyti...