Hi matt,
I have read that, but I am quite sure, that "event tracking" is possible right now, or quite easy to implement as 80% is a wrapper about existing things). I have seen, that in JS it is possible to set a scope for custom variables (page or view). I simply thought, that this part is not docuented with the REST API, but possible...
And yes, that is event tracking, but an infinity of subcategories should be easy to do. Example use case
Mobile,iOS,iOS 6,iPad,de-at
Desktop,Windows,Windows 7,Chrome,de-at
Questions you should be able to answer with these custom variables:
Piwik is frustating close to event tracking.
IMHO 2 major steps are needed
1)Allow tracking an infinite number of key/values (Please refer to example above. Expect of the first and the last one they are both, key and value)
2)A scope ONCE which makes overwriting of custom variables impossible
The third step is optional: Creating a wrapper for custom variable, which specifies the following (%abc% <-- This is a parameter, using REST API)
_cvar={“1″:["event","%abc%","%def%",...,"%ghi%"]} Custom variables with the key (first item) "event" should not be shown in custom variables report, but in a new event report (in a perfect world)...
Thanks
Florian R.
I have read that, but I am quite sure, that "event tracking" is possible right now, or quite easy to implement as 80% is a wrapper about existing things). I have seen, that in JS it is possible to set a scope for custom variables (page or view). I simply thought, that this part is not docuented with the REST API, but possible...
And yes, that is event tracking, but an infinity of subcategories should be easy to do. Example use case
Mobile,iOS,iOS 6,iPad,de-at
Desktop,Windows,Windows 7,Chrome,de-at
Questions you should be able to answer with these custom variables:
- % Mobile
- %iOS user on iPad
- %iPad users (whole userbase)
- % of e.g. fr-fr
Piwik is frustating close to event tracking.
IMHO 2 major steps are needed
1)Allow tracking an infinite number of key/values (Please refer to example above. Expect of the first and the last one they are both, key and value)
2)A scope ONCE which makes overwriting of custom variables impossible
The third step is optional: Creating a wrapper for custom variable, which specifies the following (%abc% <-- This is a parameter, using REST API)
_cvar={“1″:["event","%abc%","%def%",...,"%ghi%"]} Custom variables with the key (first item) "event" should not be shown in custom variables report, but in a new event report (in a perfect world)...
Thanks
Florian R.