-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Let users track Custom Dimensions #82
Comments
BTW: In PHP-Tracker we used a more generic implementation see: https://github.com/piwik/piwik-php-tracker/pull/15/files It's basically a method |
Curious as to the status of custom dimensions for the iOS SDK. The documentation recommends using dimensions over custom variables however this is still listed as an enhancement for the iOS library. Trying to decide the right path for some additional event tracking meta data. Thank you! |
Hi @tobz67 Maybe you are able to help us here? we would welcome a pull request to add the setCustomTrackingParameter method in the iOS SDK. In general, we welcome your help to maintain and improve our iOS SDK! |
FYI: we the Piwik team are looking for a maintainer for the iOS SDK. if you can help please comment here #91 - we need you! |
There is an open pull request on Custom Dimension tracking. Please add your thoughts. |
In matomo-org/matomo#9129 we created a new plugin to track Custom Dimensions.
To the JavaScript Tracker we added a new method
setCustomDimension(int dimensionId, string dimensionValue)
. This sets a tracking API parameterdimension$dimensionId=$dimensionValue
. Egdimension1=foo
ordimension2=bar
. So the tracking API parameter starts withdimension
followed by the setdimensionId
.I reckon we should be consistent here with the PHP Tracker and clear all set custom dimensions after the next tracking request was sent.
eg
FYI: Custom Dimensions are similar to Custom Variables. Currently a plugin is needed to use them but in Piwik 3.0 it will be installed by default and at some point we will deprecate Custom Variables (not soon though)
The text was updated successfully, but these errors were encountered: