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
optUserOut cookie expires after session #14487
Comments
See docs
that should be on purpose only during this page view or not? |
@tsteur In that case I (and the help at https://developer.matomo.org/guides/tracking-javascript-guide#optional-creating-a-custom-opt-out-form) are misunderstanding the use case for that feature. I was recommending to use The docs for Lines 7538 to 7542 in 871c31d
|
@Findus23 I don't really know how it is supposed to be used for user opt outs. The initial implementation was for consent and then some symlinks for For a custom opt out they can't really work I think since you would also need to "requireConsent" on every page load or so? Not sure. |
@Findus23 is this issue maybe then only about updating the docs? |
I’ve been trying to use this feature to create a custom opt-out form, because the one built into Matomo doesn’t work if you’re tracking sites over multiple domains (third-party cookie blockers are on by default in a few browsers now). If this cookie is a misunderstanding of the use case, perhaps the function shouldn’t be called “optUserOut” and the docs should be updated, and whatever opt-out cookie the built-in opt-out form sets should be exposed to users. My main issue at the moment is I have no reliable way for a user to opt out of tracking. Please excuse my ignorance if any of this is wrong, I’m a Matomo user and I’ve not contributed to the Matomo project before. |
Looking at this PR 6f5b85b#diff-1279d666063b65e6d6777f902d11574fR7302 it was maybe meant to be stored forever the cookie? Or what life time should we set here? From what I see we would need to set like year 2030 as it can't be stored forever. If we can make this use case work by fixing the set cookie to store it forever, I reckon we should. Mozilla actually suggests setting |
The cookie set by the new
_paq.push(['optUserOut'])
feature (mtm_consent_removed
) seems to be only valid for a session due to setting0
here:matomo/js/piwik.js
Line 7525 in 871c31d
The text was updated successfully, but these errors were encountered: