Our tracking API is fully documented at: Tracking API - tracking users analytics
It is also fully featured, and yet still a bit unstructured. Because we have added parameters one after the other when they were needed for useful features, now we realize that they could be named better, and be more structured.
Now that JSON has gone mainstream, it is natural to provide a pure JSON proxy to our good old named parameters. In the making, we could introduce structure in elements like events or ecommerce interactions (define each as a JSON object).
New API names proposals (to be discussed)
Hi @mattab ,
I've landed there from piwik/developer-documentation#28
I think you should consider using POST request for the Tracking API. Maybe you can also allow GET requests in case the client cannot do POST requests (Google Analytics does that), but the better HTTP verb to use in this case in POST (see here).
Some other thoughts:
apiv will now be passed in the URL (for instance http://mypiwik.com/api/v2/) if I understand correctly.
lang -> userLanguage?
Also, I don't know if you're familiar with JSON Schema, but it may be a good way to validate such user-submitted data.