You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'd like to develop new feature for piwik - tracking DOM user activity.
I would add new action type to piwik tracker class and create new plugin to support it. Also, I would improve the Javascript tracker to implement this new feature.
Many might think that this can be accomplished by using the existing Events in piwik, but it cannot be done without unrelated data that will be saved to piwik tables in the database.
I'm asking the project owner / founder for acceptance that this is the way piwik want to go.
Please reply, so I could think if it worth developing this feature.
The text was updated successfully, but these errors were encountered:
A real-time analytic platform apart from bulk general stats (found for example in google analytics) is absolutely required to have:
customizable real-time web desktop notifications (eg, visitor coming from a certain country, opening a certain page like registration, etc)
real-time pinging of visitors (knowing when they are actively reading/ scrolling/ writing something, with just 2-3 seconds of delay) for accurate time on page and reports
easy to implement dom activity tracking
So, from where I am standing you are tackling 1/3 of the big problem.. its not just worth it, its an absolute must-have! That is, for a "real-time" label.
Hi, I'd like to develop new feature for piwik - tracking DOM user activity.
I would add new action type to piwik tracker class and create new plugin to support it. Also, I would improve the Javascript tracker to implement this new feature.
Many might think that this can be accomplished by using the existing Events in piwik, but it cannot be done without unrelated data that will be saved to piwik tables in the database.
I'm asking the project owner / founder for acceptance that this is the way piwik want to go.
Please reply, so I could think if it worth developing this feature.
The text was updated successfully, but these errors were encountered: