This seems overkill; why would you need to track more than 2k urls? Plus the iframe solution is not really something we are ready to implement (not industry standard, more a hack). plus POSTing data is meant to be an "action", something the user clicked or validated. Thanks for feedback anyway
With the new piwik.js, we might consider using XmlHttpRequest (or IE equivalent ActiveX objects) -- for Web 2.0 goodness -- and JSON. This would permit more complex data for custom_vars and allow for non-image responses, eg server generated idvisitor.
In , fixes #5721, refs #1460 - add .setRequestMethod("POST") to piwik.js
Use cases: - workaround GET request length limit - workaround mod_security or .htaccess rules that block request containing "http"
Notes: - subject to same origin policy
In , the XmlHttpRequest is now asynchronous.
See also #2321