For enabling product usage data in the product we need a way for users to opt in to (and out of) product usage tracking.
The most suitable place for this is the global settings page which is currently in the works.
Product Brief -- includes an opt-in in the settings page, and a message to new users in the other dashboard pages (my stories, explore templates) where the user can opt-in or dismiss.
Mock:

_Do not alter or remove anything below. The following sections will be managed by moderators only._
__( 'https://policies.google.com/privacy', 'web-stories' )enableInProgressViews flag.api list in get_dashboard_settings() in Dashboard.php is extended to include /wp/v2/users/meGET request to /wp/v2/users/me is made to retrieve the current user's opt-in status from meta.web_stories_tracking_optinPOST request to /wp/v2/users/me is made to update the value of meta.web_stories_tracking_optin to true/falseSee API reference for that endpoint.
@swissspidy For now, moving into Product brief/UX needed? Looking through quickly, I don't think this has been designed, but let me know if I missed something.
@BrittanyIRL @carlos-kelly @pbakaus @samitron7 @swissspidy @dvoytenko would love your reviews on the product brief, tried to keep it simple, but with an opt in throughout so that users have a chance to quickly discover the opt-in bit and opt in.
@o-fernandez - My initial feedback: adding this to the settings view is straight forward and can easily be done!
The "new user considerations" where
We prompt new users to share their data by showing them the opt-in message at the top of the dashboard pages (My Stories and Explore Templates) and giving users the option to Opt-in or Dismiss the message.
would be outside of the settings view and should be its own thing. It will also need some design love. Could we separate these two things into their own stories so that it's more manageable?
Right now, the settings page is set up to be available to users who are admin only - with the canManageSettings config being true. This brief suggests that settings should be readable to everyone, but only updatable by admin. Either one is doable, but I wanted to bring it up so that we can get it right. The settings page has had a lot of iterations and I just don't want anything to get lost.
Before we implement opt in I think it's important that the existing settings view gets QA'd and UAT'd since it hasn't gotten a chance to go through that yet. (#4132 )
Got it, let me file a quick ticket for the banner. FYI @pbakaus @samitron7
Update: See #4226 for the banner.
@BrittanyIRL to your other points:
UX for telemetry opt-in on settings and dashboard are here
Some notes/thoughts:
X icon in the top right corner?This opt-in checkbox could also be displayed in the plugin activation message, so that we get as many users as possible to opt-in
Here's how Site Kit does it, for context:

@samitron7 WDYT?
@swissspidy - all sound feedback. I updated the banner in the dashboard to reflect the checkbox but instead of using the toast let's inline the feedback.
@oef to assist with messaging (ie use of word anonymous and do we need a ticket for a congrats banner after plugin activation?
@swissspidy - all sound feedback. I updated the banner in the dashboard to reflect the checkbox but instead of using the toast let's inline the feedback.
@OEF to assist with messaging (ie use of word anonymous and do we need a ticket for a congrats banner after plugin activation?
Connected with @samitron7 on this yesterday, she's updating.
There are about 7 of us on the assignees but I will take the development on this one.
Updates has already be completed. Let me know if you all catch anything else.
Verified in QA
On the settings screen, how do I know my selection has been saved when toggling the "Data Sharing Opt-in" checkbox? @samitron7 This is not defined in Figma.
Will close out, can do follow-up ticket for UI indicator of "saved" as needed, but I think this pattern is OK if 90%+ of the time settings successfully save without the user having to redo it. SiteKit seems to use the same pattern, though the checkbox doesn't change until the setting is fully saved, it seems.