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

GDPR Tools can not filter on data subject "Events" #14702

Closed
twanmeijerink opened this issue Jul 26, 2019 · 5 comments
Closed

GDPR Tools can not filter on data subject "Events" #14702

twanmeijerink opened this issue Jul 26, 2019 · 5 comments
Labels
wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.

Comments

@twanmeijerink
Copy link

Current situation:

  1. Register a new Event Categories, like "Feedback - Titel: home".
  2. Go to GDPR Tools
  3. Find data subjects by "Events" - "Equals" - "Feedback - Titel: home"
  4. Result: "More than 400 results were found and the result was truncated to the first 400 visits." while only 1 event is available.

Expected situation:

  1. Register an Event Categories, eg. "Feedback - Titel: home".
  2. Go to GDPR Tools
  3. Find data subjects by "Events" - "Equals" - "Feedback - Titel: home"
  4. Result: "1 result found"
@tsteur
Copy link
Member

tsteur commented Jul 28, 2019

@twanmeijerink are you using the latest version of Matomo? Cause it should actually not be possible to segment by event anymore see #12976 .

@twanmeijerink
Copy link
Author

twanmeijerink commented Jul 28, 2019 via email

@tsteur
Copy link
Member

tsteur commented Jul 28, 2019

It's a performance reason. It would be a lot of trouble for most Matomo databases out there scanning the entire database of all visitors/actions that were ever taken for specific events. And with events you usually can't really identify a user. You would rather use a custom dimension or userId or so to identify a specific visitor. Or do you record personal data like an email address in events?

@twanmeijerink
Copy link
Author

Yes, we record emailaddres in events.. :-(

@tsteur
Copy link
Member

tsteur commented Aug 7, 2019

Any chance you could save it as a visit custom dimension or userId on top? We're actually not planning on allowing to filter by events for performance reason. I'm sorry but I'll have to close the issue for now. I highly recommend ideally setting it eg as a visit custom dimension (additionally if needed). This will allow you to filter for it.

@tsteur tsteur closed this as completed Aug 7, 2019
@tsteur tsteur added the wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it. label Aug 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Projects
None yet
Development

No branches or pull requests

2 participants