-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[Desktop] Follow up to #11057: Implement client ads pacing mechanism #11643
Comments
Please check https://github.com/brave/brave-core/blob/master/vendor/bat-native-ads/src/bat/ads/internal/eligible_ads/eligible_ads_pacing_filter.cc as the value is a |
Verification passed on
Verified test plan from https://github.com/brave/internal/issues/720 Ads pacing - PTR = 0
Ads pacing - PTR=0 to PTR=1 through catalog update
Ads pacing - PTR = 0.5 - untargated
Ads pacing - PTR = 0.5 - Technology & Computing
Verified passed with
Ads pacing - PTR = 0
Ads pacing - PTR=0 to PTR=1 through catalog update
Ads pacing - PTR = 0.5 - untargated 50 eligible ads before pacing
Ads pacing - PTR = 0.5 - Technology & Computing 20 eligible ads before pacing
Verification passed on
Verified test plan from https://github.com/brave/internal/issues/720 Ads pacing - PTR = 0
Ads pacing - PTR=0 to PTR=1 through catalog update
Ads pacing - PTR = 0.5 - untargated
Ads pacing - PTR = 0.5 - Technology & Computing
|
Follow up to #11057. Implement client ads pacing mechanism.
The ads are always shown, even when PTR is 0.
Steps to Reproduce
Actual result:
Ads are shown
Expected result:
Ads are not shown, because PTR is 0
Reproduces how often:
Easily reproduced
Brave version (brave://version info)
cc @brave/legacy_qa @rebron @AndriusA @tmancey @jsecretan
The text was updated successfully, but these errors were encountered: