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
Comments
@twanmeijerink are you using the latest version of Matomo? Cause it should actually not be possible to segment by event anymore see #12976 . |
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)
@twanmeijerink<https://github.com/twanmeijerink> are you using the latest version of Matomo? Cause it should actually not be possible to segment by event anymore see #12976<#12976> .
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#14702?email_source=notifications&email_token=ACDTRSUERA2BMMJMDKKGHG3QBYCVZA5CNFSM4IHCDIH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD27GQ2I#issuecomment-515795049>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ACDTRSVAQPWQPJ7A7ZPHR3TQBYCVZANCNFSM4IHCDIHQ>.
|
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? |
Yes, we record emailaddres in events.. :-( |
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. |
Current situation:
Expected situation:
The text was updated successfully, but these errors were encountered: