Navigation Menu

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

Jump to bottom

Show "content interactions" in vistor log #10052

Closed
hpvd opened this issue Apr 14, 2016 · 3 comments
Closed

Show "content interactions" in vistor log #10052

hpvd opened this issue Apr 14, 2016 · 3 comments
Labels
duplicate For issues that already existed in our issue tracker and were reported previously.

Comments

@hpvd
Copy link

hpvd commented Apr 14, 2016

Content tracking is a good thing! (For details see: https://piwik.org/docs/content-tracking/)
To get even more informations from this implementation, it would be good to show "content interactions" in visitor log similar to events (maybe only using another symbol)

This would give the possibility to understand which way the visitor has taken to go from one site to an other:

  • does he use the mega-drop-down menu in head of page?
  • does he use the "related article links" located at the end of the article?
  • does he use the "next article" link?
  • does he use the news box on the right side?
  • does he use the links within the text of the article?
@hpvd hpvd mentioned this issue Apr 14, 2016
Closed
@hpvd
Copy link
Author

hpvd commented Apr 14, 2016

in addition to understand which way a user has used, it may give also an inside about his motivation:
Just an example:
if he uses "related article links" which shows name and image of an related article, he is much more focused and intersted in the content of the related article
than if he uses "next article" link which brings him to an unpreknown type of artikle...

@tsteur
Copy link
Member

tsteur commented Apr 14, 2016

Thanks @hpvd I'll mark this one as a duplicate of #6416

We'll have a look at this one again when working on #6416

@tsteur tsteur closed this as completed Apr 14, 2016
@tsteur tsteur added the duplicate For issues that already existed in our issue tracker and were reported previously. label Apr 14, 2016
@hpvd hpvd mentioned this issue Apr 15, 2016
Closed
@hpvd
Copy link
Author

hpvd commented Apr 18, 2016

an idea how this can look:
2016-04-18_08h00_18

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate For issues that already existed in our issue tracker and were reported previously.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tsteur @hpvd