For example in this documentation: http://piwik.org/docs/ecommerce-analytics/#tracking-ecommerce-orders-items-purchased-required

we recommend the following (currently):

_paq.push(['trackEcommerceOrder',
.....
]);
_paq.push(['trackPageView']);
[...]

so the idea would be to bulk those two requests in one bulk request.

we need to pick a timer delay (eg. 100ms), the piwik.js queue will wait for this timer to "collect" other pushed requests, and then will send as bulk if there is more than one queued.

Note: in Contents tracking plugin Thomas used this technique to send a bulk request. This was done in: 774611a

See piwik.js tracking function function sendBulkRequest(requests, delay) {

After a few experiments with piwik, I can confirm that the bug still exists. When a mix of events and page visits happen nearly simultaneously, it is likely that they are put to the database in the wrong order. The issue seems to be simply caused by different speeds of HTTP requests. Having that sendBulkRequest() already exists in piwik.js, how difficult would it be to fix the processing of a set of _paq.push() calls? The source code appears to have all necessary components, the only thing needed is to throttle the activity behind _paq.push().

I'm new to piwik, so I'm afraid I'll be only able to implement some dirty solution if any at all. If anyone knowledgeable in piwik.js sees this, your help will make a real difference. Hope it's an easy pick.

At this point it seems better not to implement this feature, as otherwise it would lead to many POST requests to the Tracking API which is not desired because it would prevent us from Replaying the tracking requests later on, in case of a Piwik server problem. Wont fix.

This issue has been mentioned on Matomo forums. There might be relevant details there:

https://forum.matomo.org/t/javascript-react-bulk-sending-events/50498/1

@mattab What if we store client time for each event and send to Matomo? So we still only need 1 POST request but the time still correct.

Also I would like to have a setting to define which event will not being put in bulk request (Example with purchase event, it better being sent immediately instead of waiting for a delay and user close page before events could be sent)?