In our company we've designed a website were we are going to use infinite scroll on section pages but also on article pages. When the article page is loaded it will load the first 3 articles. The visitor can now scroll through these articles and read them. When the visitor gets at the second half of the 3rd article the next 3 articles are automatically loaded in the background. This way the visitor can read articles without having to click.
The problem now is what the best way would be to measure this in Adobe Analytics (Omniture SC15). Our business want to know which article is loaded and hopefully read. The website is still in development but there is a website called www.qz.com who works the same as what we want to do.
I'd love to see you guys provide some thought leadership around this topic as more and more publishers move to the infinite scroll structure. It seems like there should be a good standardized approach to how we track this functionality using Adobe Analytics. I'm still trying to wrap my brain around what exactly I'll want to be able to provide insight into when we begin implementing this functionality later this year, and then how we should be implementing to be able to facilitate this.
A few off the top of my head questions I'll want to answer:
* what position a piece of content was in when viewed. E.g. if articleX got 150 pageviews (assuming we'll increment pageviews for each item entering viewport within infinite scroll), how many pageviews occurred with that article in position 1 vs. position 3 ?
* how does position within infinite scroll affect time on page (e.g. what is average time on page for content in position 1 vs. position 3?)
* how does position affect level of interaction with content -- if longer content is truncated and a "read more" link is included, how does position within infinite scroll impact user engagement with those links?
I'll also want to ensure I'm able to cleanly delineate referrals to a piece of content (internal and external referrals) to only include items in first position, as obviously the first item viewed would be the item the user intended to reach.
This is obviously just the tip of the iceberg. I would love to hear from others who are wrestling with similar problems, and most ideally would love to get some centralized guidance from Adobe on how publishers should approach measurement of infinite scroll.