Replies: 3 comments 8 replies
-
Beta Was this translation helpful? Give feedback.
6 replies
-
@zackkrida Is this discussion still in progress? It is marked high priority but has no activity for the last two weeks and is over a month old now. |
Beta Was this translation helpful? Give feedback.
1 reply
-
This discussion has already been resolved and the recommended changes have already been developed and merged to the frontend:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Due date: 2023-05-10
Assigned reviewers
Description
For the #394 project we need to allow users to opt-out of analytics tracking. This will allow users to opt out of page view and custom event tracking. Currently, we do not allow users to opt out of the page view tracking we collect via Cloudflare Analytics, so this change gives more flexibility and freedom to users than we currently offer.
One goal of this interface is to avoid bloating the scope of the analytics project as much as possible. To that aim, I've proposed the following approach:
This allows us to quickly create an acceptable flow using existing components and routes, without needing any custom UI, a dedicated implementation plan, or any design work (beyond choosing copy and color of the banner, and placement of the toggle on the privacy page [before or after the existing copy]).
Is this an acceptable solution? What do you think? If the two proposed reviewers of this discussion approve the idea, I'd like to fast-track this and close the discussion before the indicated date.
Beta Was this translation helpful? Give feedback.
All reactions