We know there is a limitation in Piwik and it can not record more than 1 goal per second (it is documented in the file GoalRequestProcessor function afterRequestProcessed).
What changes should be made in order to avoid this limitation?
We need to record more than one goal per second for the same visit.
Any ideas on where this limitation is implemented so we can skip it while we think a better way to do it right in Piwik?
Is it at DB level or in the code?
Let me know if we provided all the information needed.
It’s rather a question to core developers. Most likely it was limited because of some race condition and IMO it would be nice to have this fixed in Piwik 3.0.
Thank you. We did more research last week and the limitation is basically from the conversion table. The primary key is based on idvisit, idgoal and buster. We deleted the and now it works perfectly. We can save several conversion per second by the same user and visit.
I’m not sure why there is this limit since it would make not much sense for us.
Hope somebody from the core could explain it. Any idea on how to get their attention on this topic?
In the meantime what we have done drop the PK for the conversions table. We did that change in a plugin.
Since then it has worked for us but on a few occasions we got duplicated conversions.