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
Content impressions generate "0 Action" in visitor log #6415
Comments
Thanks for the report! Bug:
Note: I also created a new issue after seeing the screenshot: Content-tracking: display content views and interactions in the Visitor log #6416 |
This should be fixed in #6296 |
@hmage please test with latest Piwik beta version: http://piwik.org/faq/how-to-update/faq_159/ If you still experience the issue please reopen this ticket! thanks for your tests. |
Will test tomorrow. Is there a way to clean up the data that already got into the system? |
Ah bummer the bug is not fixed |
After some digging — now it happens once per user. To force the “0 Action” I need to clear out the cookies and visit the site again. |
Also, will be there a way to cleanup the generated events? Maybe some mysql query that I can run manually? |
…is used. Delay first content tracking request a bit to make kinda sure a possible previous pageview request is already executed. If there is a new visitor and there are 2 tracking requests at nearly same time (eg trackPageView and trackContentImpression) 2 visits will be created as both visitors are basically at the same time. This is only a workaround and it this problem might still occur. Also delay a link earlier in case an interaction is happening to make sure the browser waits for the interaction to be tracked.
We will now always wait 800ms after a first tracking request was issued. This should give enough time to create a visitor before any other request is executed. Ideally we will resolve this issue on the server side as this problem can occur using other SDKs as well and for some servers or sometimes the 800ms might be not long enough.
Notes:
|
@tsteur what do you think is the status & next step of this Bug? |
From my point of view it can be closed. You wanted to leave it open so users can find it |
The bug is still actually live, leaving opened WORKAROUND: use QueuedTracking plugin with Redis should fix this issue: http://plugins.piwik.org/QueuedTracking |
Hi, after implementing content tracking I started to get visits with 0 Actions and my Bounce Rate is being seriously affected. I´m using the 2.15.0 Version and the issue is still there. Thanks, JCM77 |
Hi Matt, we installed the plug-in and unfortunately we still have the problem. We keep looking for ways to solve the issue, one of them could be to disable the content tracking and see if the problem persists. I will let you know if we can solve it Regards Javier |
hmm is there any news/solution on this? |
The only known workaround is to use the QueuedTracking plugin see #6415 (comment) |
@tsteur I meet this issue, when I update to 3.4.0. show many 0 action. and In my develop server, it is not many request, but it still show 0 action. Have you help me see the issue? thanks, Sophie Wang |
See one comment above. Give the plugin Queued Tracking a try. It is now easy to set it up and likely fixes all the issues. |
I haven't over all the comments but wouldn't a similar solution that we do to avoid duplicate actions do?
Haven't thought much about it though but something like this could work here too? But of course it be another select for new visits. @mattab |
This might work 👍 This issue is valuable because ideally we wouldn't want people to have to use QueuedTracking to solve an issue. |
FYI: The solution: Give the plugin Queued Tracking a try. This should fix this issue.As it has been a few months since the last activity and we believe this is likely not an issue anymore, we will now close this. If that's not the case, please do feel free to either reopen this issue or open a new one. We will gladly take a look again! |
After adding the content impression, my visitor log got spammed with "0 Action" entries.
I don't think this is intended, so I'm opening an issue.
Images with links are marked something like this:
The text was updated successfully, but these errors were encountered: