@mattab opened this Issue on September 1st 2020 Member

More and more people are disabling tracking cookies (we sometimes call it cookie-less tracking), because no cookie consent is needed then.

When cookie-less tracking is enabled some features don't work for example:

  • Unique Visitors metric is very inaccurate
  • New VS Returning visitors
  • Goals and Ecommerce conversions will be attributed to the channel used in the visit that converts
  • Some reports are very inaccurate:
    • Days since last visit,
    • Visits by visit count,
    • Visits to Conversion,
    • Days to Conversion
    • Cohorts
    • Multi Attribution

Because the features become very broken after cookie-less is enabled, people tend to get confused, and ask questions, or they may use the data not knowing it's very wrong! So it would be really useful to somehow hide these reports from users, or make it otherwise crystal clear that they shouldn't use this data. What do you think?

Note: we'd leave Visitor profile as it's helpful when user id is used

required for https://github.com/matomo-org/matomo/issues/15507

@tsteur commented on September 3rd 2020 Member

Hiding this data was also suggested in https://github.com/matomo-org/matomo/issues/13655#issuecomment-616892565 but we didn't do it since it can currently not be enforced and is only done client side. There are few more features like Cohorts, Multi Attribution, Visitor Profile, etc. Hiding this features might only be a good idea though if not also the userId feature is used.

This feature will only work when cookies can be disabled server side eg see https://github.com/matomo-org/matomo/issues/16258 . We could look at making this work after #16258 was developed

Powered by GitHub Issue Mirror