Skip to content
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

setCustomData(): How to fire custom data to custom plugin? #2206

Closed
anonymous-matomo-user opened this issue Mar 19, 2011 · 2 comments
Closed
Labels
Bug For errors / faults / flaws / inconsistencies etc. Critical Indicates the severity of an issue is very critical and the issue has a very high priority. worksforme The issue cannot be reproduced and things work as intended.
Milestone

Comments

@anonymous-matomo-user
Copy link

I'm using SiteSearch plugin https://github.com/BeezyT/piwik-sitesearch/wiki and it's documented to fire the number of search results via piwikTracker.setCustomData({SiteSearch_Results: XX}); to the plugin. As setCustomData() has been deprecated and I have no idea - why - it's now in question - how a custom plugin can get custom data it needs to build a statistic. setCustomVariable() is no option here as it only allows up to 5 slots and the names and values are shown in custom variables statistics and does not go into the custom plugin (SiteSearch) statistic.

Normally you see in SiteSearch a table with keywords and than a column with the number of search results for this keyword.

@robocoder
Copy link
Contributor

Answered in #1984. Consider it un-deprecated for the time being.

@timo-bes
Copy link
Member

If you remove setCustomData(), please let me know in advance, so I can update the SiteSearch plugin.
Of course, there should be an alternative way to pass the custom data...

@anonymous-matomo-user anonymous-matomo-user added this to the Piwik 1.3 milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. Critical Indicates the severity of an issue is very critical and the issue has a very high priority. worksforme The issue cannot be reproduced and things work as intended.
Projects
None yet
Development

No branches or pull requests

4 participants