How should we present analytics opt-out in the frontend user interface?

[zackkrida]

Due date: 2023-05-10

Assigned reviewers

• @fcoveram
• @dhruvkb

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:

• Add a banner to the top of Openverse which says "Openverse uses analytics to improve the quality of the service. Visit our privacy page to opt-out." and which has "opt out" and "Allow" buttons.

• Add the existing analytics feature flag from the preferences page (https://staging.openverse.org/preferences) to the privacy page

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.