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

Content impressions generate "0 Action" in visitor log #6415

Closed
hmage opened this issue Oct 10, 2014 · 30 comments
Closed

Content impressions generate "0 Action" in visitor log #6415

hmage opened this issue Oct 10, 2014 · 30 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org.

Comments

@hmage
Copy link

hmage commented Oct 10, 2014

After adding the content impression, my visitor log got spammed with "0 Action" entries.

image

I don't think this is intended, so I'm opening an issue.

Images with links are marked something like this:

<a target="_blank" href="images/image-104.jpg" data-track-content 
   data-content-name="Image #104">
<img src="images/image-104-thumb.jpg" alt="Image #104" data-content-piece/>
</a>
@mattab mattab added this to the Piwik 2.9.0 milestone Oct 10, 2014
@mattab mattab added the Bug For errors / faults / flaws / inconsistencies etc. label Oct 10, 2014
@mattab
Copy link
Member

mattab commented Oct 10, 2014

Thanks for the report!

Bug:

  • multiple visits are created when tracking Contents views, instead of tracking all views in the same visit.

Note: I also created a new issue after seeing the screenshot: Content-tracking: display content views and interactions in the Visitor log #6416

@tsteur
Copy link
Member

tsteur commented Oct 12, 2014

This should be fixed in #6296

@mattab
Copy link
Member

mattab commented Oct 12, 2014

@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.

@mattab mattab closed this as completed Oct 12, 2014
@mattab mattab added the duplicate For issues that already existed in our issue tracker and were reported previously. label Oct 12, 2014
@hmage
Copy link
Author

hmage commented Oct 12, 2014

Will test tomorrow. Is there a way to clean up the data that already got into the system?

@hmage
Copy link
Author

hmage commented Oct 12, 2014

Ok, after installing and updating — I still get “0 action” events, but far less frequently.

Don’t have access to reopen the ticket. So commenting here with hope that you’ll notice this and reopen it.

screen shot 2014-10-13 at 03 16 48
screen shot 2014-10-13 at 03 17 35

@mattab mattab reopened this Oct 13, 2014
@mattab
Copy link
Member

mattab commented Oct 13, 2014

Ah bummer the bug is not fixed

@mattab mattab added the Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. label Oct 13, 2014
@mattab mattab modified the milestones: Piwik 2.8.0, Piwik 2.9.0 Oct 13, 2014
@mattab mattab removed the duplicate For issues that already existed in our issue tracker and were reported previously. label Oct 13, 2014
@hmage
Copy link
Author

hmage commented Oct 13, 2014

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.

@hmage
Copy link
Author

hmage commented Oct 13, 2014

Also, will be there a way to cleanup the generated events? Maybe some mysql query that I can run manually?

tsteur added a commit that referenced this issue Oct 13, 2014
…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.
@tsteur tsteur self-assigned this Oct 14, 2014
tsteur added a commit that referenced this issue Oct 14, 2014
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.
@mattab mattab modified the milestones: Piwik 2.9.0, Piwik 2.8.0 Oct 14, 2014
@mattab
Copy link
Member

mattab commented Oct 14, 2014

Notes:

  • this bug should only occur in a small percentage of cases.
  • unfortunately so far I can't think of any solution to the problem of multiple tracking requests in the same second causing multiple visits.
  • maybe the easiest way is to implement queue Write tracking requests into a queue and don't process them immediately  #6075 so that we can import all requests for a same { person / visitor / user } all at once?

@mattab mattab modified the milestones: Short term, Piwik 2.9.0 Oct 14, 2014
@mattab
Copy link
Member

mattab commented Apr 7, 2015

@tsteur what do you think is the status & next step of this Bug?

@tsteur
Copy link
Member

tsteur commented Apr 7, 2015

From my point of view it can be closed. You wanted to leave it open so users can find it

@mattab mattab closed this as completed Apr 7, 2015
@mattab mattab added the worksforme The issue cannot be reproduced and things work as intended. label Apr 7, 2015
@mattab
Copy link
Member

mattab commented Nov 25, 2015

The bug is still actually live, leaving opened

WORKAROUND: use QueuedTracking plugin with Redis should fix this issue: http://plugins.piwik.org/QueuedTracking

@mattab mattab reopened this Nov 25, 2015
@mattab mattab removed the worksforme The issue cannot be reproduced and things work as intended. label Nov 25, 2015
@mattab mattab modified the milestones: Mid term, Short term Nov 25, 2015
@jcm77
Copy link

jcm77 commented Nov 26, 2015

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.
I will see if this http://plugins.piwik.org/QueuedTracking works.

Thanks,

JCM77

@jcm77
Copy link

jcm77 commented Dec 2, 2015

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

@hpvd
Copy link

hpvd commented Jul 15, 2016

hmm is there any news/solution on this?
would be awesome to share it here.

@tsteur
Copy link
Member

tsteur commented Jul 17, 2016

The only known workaround is to use the QueuedTracking plugin see #6415 (comment)

@mattab mattab modified the milestones: Mid term, Long term Dec 5, 2016
@huang0808
Copy link

@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

@tsteur
Copy link
Member

tsteur commented Jul 26, 2018

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.

@tsteur
Copy link
Member

tsteur commented Aug 17, 2019

I haven't over all the comments but wouldn't a similar solution that we do to avoid duplicate actions do?

  • Like we insert the visit
  • then we select like all visits that were created in the last 1 min matching the config_id or the visitor_id (depending on the config settings, config_id match has index and is fast anyway)
  • we only keep the visit with the lowest id or so.

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

@mattab
Copy link
Member

mattab commented Oct 21, 2019

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.

@mattab
Copy link
Member

mattab commented Dec 11, 2023

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!

@mattab mattab closed this as not planned Won't fix, can't repro, duplicate, stale Dec 11, 2023
@sgiehl sgiehl added the not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org. label Dec 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org.
Projects
None yet
Development

No branches or pull requests

8 participants