@Findus23 opened this Issue on May 27th 2019 Member

The cookie set by the new _paq.push(['optUserOut']) feature (mtm_consent_removed) seems to be only valid for a session due to setting 0 here:

@mattab commented on May 27th 2019 Member
@tsteur commented on May 27th 2019 Member

See docs

         * Calling this method will remove any previously given consent and during this page view no request
  • will be sent anymore ({@link requireConsent()}) will be called automatically to ensure the removed
  • consent will be enforced. You may call this method if the user removes consent manually, or if you
  • want to re-ask for consent after a specific time period.

that should be on purpose only during this page view or not?

@Findus23 commented on May 28th 2019 Member

@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 optUserOut to people who had issues as their Matomo is on a different and therefore the opt-out iFrame isn't working as most browsers block third-party-cookies.
Also for people who wanted to customize the look of their opt-out more than it is possible with an iFrame.

The docs for optUserOut also seem to indicate this use case:

@tsteur commented on May 28th 2019 Member

@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 userOptOut and forgetUserOptOut was added. Not sure how much these actually work. Maybe it was misunderstood how these methods behave when adding the symlinks.

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.

Powered by GitHub Issue Mirror