Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

we have no "time on url": Piwik handels events as leaving page (at least in visitor log) #11546

Closed
hpvd opened this issue Mar 28, 2017 · 14 comments
Labels
duplicate For issues that already existed in our issue tracker and were reported previously.

Comments

@hpvd
Copy link

hpvd commented Mar 28, 2017

we have no "time on url": Piwik handels events as leaving page (at least in visitor log)
how is it handled on other places within piwik?

.. and some other thoughts derived from this #11546 (comment)

2017-03-28_12h36_23

what is the consequence?

Example:

Different "Only one page visitors" visits two different pages
with both containing:

  • text
  • images
  • large version of images in lightbox
  • lightbox usages is tracked via event (open LB, next image etc...)

The difference:
page 1:
great long text + many good images (starting explaining content of the text)

page 2:
great long text + many awesome images (colorfull, well structured, explaining content of the text, great captions)

what happens?

on page 1:
people coming to the site
will read the text and
after some time,
some will look at
a part of the large versions of the images (they know the content because of reading the text)
(open light box = event)

on page 2:
people coming to the site
will directly look at the large versions of the images (open light box = event)
look at the details,
read their captions
etc
after that some will read the first part of the text
(they know the content because of looking at images and reading their captions)

Results shown in Piwik (visitor log):
Page 1: 6 minute [avarage] (+ some short events)
Page 2: 1 minute [avarage] (+ many long events)

so what do I gather from this as website owner?
Page 1 is far better
page 2 needs optimization

with this
=> I have no chance to notice that full visit time maybe even longer on page 2.

@hpvd
Copy link
Author

hpvd commented Mar 28, 2017

what would one need:

  1. a possibility to know "full time on page" (including all events)
    imho: this should be the base for all metrics.
    isn't the thing we want to know something like ="time on url"?

  2. a possibility to measure "time directly on page" for cases where there are events opening a new "layer" on same url which hides the content of the page and bring up new content on same url:
    for this one need some kind of marker within an event (open new layer + close layer)
    with this:
    "time directly on page" = "full time on page" - "time between event with marker opening a new layer and event with marker closing new layer"

  3. hmm maybe only a nomenclature thing: do events really have a duration or do we track here something like "time between actions"?
    if so, one could think of naming it

  • "event time" e.g.: 27. March, 22:03:06
  • "time till next action" e.g. 50 seconds

@hpvd hpvd changed the title Piwik handels events as leaving page (at least in visitor log) Piwik handels events as leaving page (at least in visitor log) -> we have no "time on url" Mar 28, 2017
@hpvd hpvd changed the title Piwik handels events as leaving page (at least in visitor log) -> we have no "time on url" we have no "time on url": Piwik handels events as leaving page (at least in visitor log) Mar 28, 2017
@mattab
Copy link
Member

mattab commented May 8, 2017

Hi @hpvd

I may be wrong, but it sounds like the solution is simply to use the Heart beat timer. please find more information here: https://developer.piwik.org/guides/tracking-javascript-guide#accurately-measure-the-time-spent-on-each-page

@mattab mattab closed this as completed May 8, 2017
@mattab mattab added the answered For when a question was asked and we referred to forum or answered it. label May 8, 2017
@hpvd
Copy link
Author

hpvd commented May 8, 2017

hmmm- heart-beat timer is in use.
One can easily proof this, because also very short one page visits show a duration in the headline of the visit in visitorlog

@hpvd
Copy link
Author

hpvd commented May 8, 2017

so there is no solution yet,

@mattab
Copy link
Member

mattab commented May 8, 2017

If heartbeat timer is in use, then the time on page should be accurate. unless the feature does not work for some reason?

@mattab mattab reopened this May 8, 2017
@hpvd
Copy link
Author

hpvd commented May 8, 2017

as described, time on page is only fine in the headline (sum) of a visit in vistor log, but not for the single url within the visit.

@mattab
Copy link
Member

mattab commented May 8, 2017

@hpvd Do you mind reporting a simple list of steps to reproduce the issue? Ie. track page view, track event, track event, wait 1 min, Expected to see XYZ, Got instead: ABC. Would be very helpful and we'll take a look.

@mattab mattab added this to the Priority Backlog (Help wanted) milestone May 8, 2017
@mattab mattab added Waiting for user feedback Indicates the Matomo team is waiting for feedback from the author or other users. and removed answered For when a question was asked and we referred to forum or answered it. labels May 8, 2017
@hpvd
Copy link
Author

hpvd commented May 8, 2017

  1. have a visit with only one page view,
  2. some events (triggered at this page)
  3. leave.

=> time in headline of the visit (summary) in visitor log is fine.
=> time shown on hover on page is time until first event happen.

=> imho: would expect to see on hover on a page the total / full time on page until this page is left. No matter if there are any events during page view or not.
imho: THIS should be the base for all page time specific metrics.
see 1) in #11546 (comment)

@hpvd
Copy link
Author

hpvd commented May 8, 2017

imho: mostly, events shoud be a "child" or "subpart" of the time on a page
see 1) in #11546 (comment)

@hpvd
Copy link
Author

hpvd commented May 8, 2017

@hpvd
Copy link
Author

hpvd commented May 8, 2017

with this, in the actual implementation:
Tracking of events, shorten the measured time on page.

@jarrodldavis
Copy link

I think I'm having the same issue as @hpvd – if a page view has subsequent events, the page view time is only measured as the time between the initial page view and the first event. Essentially, every event is counted as a separate "page" rather than sub-events of the page they occurred on.

@hpvd
Copy link
Author

hpvd commented Jun 6, 2017

Possibly there is a strong relationship to: #9198

@sgiehl
Copy link
Member

sgiehl commented Oct 9, 2023

This behavior should be meanwhile improved with #18294
Everything else should be covered in of #9198

@sgiehl sgiehl closed this as not planned Won't fix, can't repro, duplicate, stale Oct 9, 2023
@sgiehl sgiehl added duplicate For issues that already existed in our issue tracker and were reported previously. and removed Waiting for user feedback Indicates the Matomo team is waiting for feedback from the author or other users. labels Oct 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate For issues that already existed in our issue tracker and were reported previously.
Projects
None yet
Development

No branches or pull requests

4 participants