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
3.12 - Custom Variable includes wrong data #15137
Comments
Afaik |
From what I saw in piwik.js, it calls |
Ok. So you expect the value to be something like |
I might be misunderstanding but this might be related to #11900 which we fixed in 3.12 and is now expected behaviour. Say you segment "value = economy" then before it would have only shown these custom variables in the report, or only page urls that had this particular custom variable. But now we have fixed the behaviour of segments to also show all custom variables and page urls of a visit that had the "custom variable value = economy". This is expected and how the segment feature should work. It basically no longer acts as a filter, but as an actual segment now. So it would be expected that when you go to the custom variables report, that you also see other custom variables values. |
Yes, so I can then filter by the articles that contain
I've tried by value and by name.
Consulting the visitor log, this seems to be what is happening. Also, given that we have ~2 to ~4 pages per session, most of the time in different category articles, by what you said, it would make sense that all pages of a visit would be listed when segmenting by category. That would make sense in a How can I "restore" the old behavior and effectively filter the page views by category? Also, The report I'm using is in the |
@DDrjm it's expected behaviour also in page scope. AFAIK Google Analytics for example behaves the same. You can restore old behaviour by setting a config setting in your [General]
enable_segments_cache = 0 but we likely remove this in Matomo 4. We don't have filters yet in Matomo which is what you want. They are not needed so often though that's why it has rather low priority. Another workaround be to use Custom Reports |
I'm currently using CustomVariable tracking on one website in order to track multiple article categories at the same time.
I have a report segment setup setup in the following way in the interface
On the website I'm tracking the Custom Variable as follows:
_paq.push(['setCustomVariable', 1, "Category", ['economy', 'highlight'], scope="page"]);
I've double checked the values set on the website, and I'm seeing articles that correspond to an unrelated category, for example science, and that are classified as science, appear on the economy segment.
How can I fix this?
The text was updated successfully, but these errors were encountered: