Implement P3A RewardsEnabledDuration
See original GitHub issueAdd a new P3A key to record how long Brave Rewards had been enabled when they’re disabled.
Question: If you have turned off BR, how long did you have it on?
Brave.Rewards.EnabledDuration
- It was never on
- It’s still on
- 1 hour
- 1 day
- 1 week
- 1 month
- More than one month
See the corresponding PR for a test plan.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:8
Top Results From Across the Web
Update P3A rewards enabled question to measure ads · Issue ...
My intuition is that "resetting Brave Rewards" doesn't count as disabling Brave Ads, so it doesn't need to be a QA test case...
Read more >Fix errors on reading long decimal floats - Ultrajson/Ultrajson
Implement P3A RewardsEnabledDuration, 8, 2021-09-27, 2022-09-27. query parameter for vrf and network does not provide information, 5, 2021-10-14, 2022-09-30.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
As discussed with @rillian in the P3A meeting, removing the milestone and QA blocked label from the issue. The follow-up issues are logged to address the issue https://github.com/brave/brave-browser/issues/21017 and https://github.com/brave/brave-browser/issues/21030
QA Blocked until the issue https://github.com/brave/brave-browser/issues/21017 is fixed