-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove P3A protobuf reporting #23902
Comments
@rillian I need clarification on p2a metrics. p2a metrics are recorded only when rewards is enabled and view an ad. It's behaving the same in both 1.41 and 1.42. But earlier it was not like that, we used to get the p2a metrics after 15 or 20 mins of browser load (p2a metrics records verified in 1.36 #15967) Is this a recent change? |
@GeetaSarvadnya are you saying in 1.36 you see P2A metrics in the first ~10 minutes without having to enable rewards and browse long enough to trigger an ad? I'm not aware of anything changing the in P2A scheduling, but the ad code which reports opportunities and impressions has changed, particularly with Brave News, so maybe that's the origin of the change? @tmancey you refactored the p2a reporting recently. Is this an expected change between 1.36 and 1.41? |
@rillian p2a metrics have not changed, just moved in the code. However, users can join Brave News ads without joining rewards and P2A are sent for ad impressions for those ads. So it could be that Brave News has changed and the ads are viewed much sooner. |
@rillian Yes @tmancey Right now P2A metrics are shown only when rewards is enabled and the ad is viewed. I have not checked p2a records after enabling brave news, let me check that as well |
At least it sounds like an improvement instead of a regression. |
@GeetaSarvadnya I do not believe this is a regression. |
@GeetaSarvadnya nothing has changed with regards to p2a in ads lib for quite a while. More than happy to jump on screen-share to go over your results. Thanks |
Verification passed on Oppo Reno 5 with Android 12 running 1.42.85 x64 build
|
Description
Reverting P3A protobuf submission is done via the PR brave/brave-core#14015 and which resolves the issue #23754 and the same is verified in 1.41.x #23754 (comment) and ensured P3A and P2A work as it works in 1.40.x
The actual fix for
Remove P3A protobuf reporting
is merged in 1.42.x and 1.43.x via the PR brave/brave-core#14017 hence created this issue to addressRemove P3A protobuf reporting
in 1.42.xTest Plan:
Run browser under a network proxy for traffic inspection
Brave.P3A.*
reports.Miscellaneous Information:
Discussed with @kjozwiak and created the issue.
cc: @brave/legacy_qa @rillian @mattmcalister @rebron
The text was updated successfully, but these errors were encountered: