Be interpreted? As we will see, the information provided by this metric, especially in the case of landing pages, can often be incomplete if we do not understand how the measurement was taken. But let's do it in order. How to calculate time? Simplified, we can say from click to click: a click is any call made, so for example when a page is loaded, a click (if internal or properly configured, see below) or an event is fired, the date of the action is recorded and time, and calculate the distance between them.
This range is the average time on page. Imagine Latest Mailing Database landing on a blog page at o'clock. Read an article, view another on a topic of interest to you in related articles, open a new page, and close it without interacting with other links. In these steps, record the first page load, link click and the second page load. So you'll get: page: min class page: ? Duration not received. The page exits for will not match any hits, so the session duration for will be.
This means two consequences: the average duration of a website session will not take into account navigation on exit pages; for landing pages or navigation on a single page, without a second page to determine exit time, it must take into account how the data is measured to Interpret the data. How to prevent this from happening? The easiest option is to create an event that provides a second click to calculate the duration on the page. Events are interactions that can be tracked whether or not a webpage or screen loads. A couple of things can help us: Scrolling on the page This event is tied to the user's activity: if he scrolls the page to continue reading.