@twanmeijerink opened this Issue on July 26th 2019

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 commented on July 28th 2019 Member

@twanmeijerink are you using the latest version of Matomo? Cause it should actually not be possible to segment by event anymore see https://github.com/matomo-org/matomo/issues/12976 .

@twanmeijerink commented on July 28th 2019

Ah ok, no on 3.9.
Is there a specific reason not to include events? Events are perfect to store any kind of data ofcourse..

Met vriendelijke groet,
Twan Meijerink


Van: Thomas Steur <notifications@github.com>
Verzonden: zondag, juli 28, 2019 11:04 PM
Aan: matomo-org/matomo
CC: twanmeijerink; Mention
Onderwerp: Re: [matomo-org/matomo] GDPR Tools can not filter on data subject "Events" (#14702)

@twanmeijerinkhttps://github.com/twanmeijerink are you using the latest version of Matomo? Cause it should actually not be possible to segment by event anymore see #12976https://github.com/matomo-org/matomo/issues/12976 .


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/matomo-org/matomo/issues/14702?email_source=notifications&email_token=ACDTRSUERA2BMMJMDKKGHG3QBYCVZA5CNFSM4IHCDIH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD27GQ2I#issuecomment-515795049, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACDTRSVAQPWQPJ7A7ZPHR3TQBYCVZANCNFSM4IHCDIHQ.

@tsteur commented on July 28th 2019 Member

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 commented on August 7th 2019

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

@tsteur commented on August 7th 2019 Member

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.

This Issue was closed on August 7th 2019
Powered by GitHub Issue Mirror