-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Round-robin Brave Ads campaign advertisers to reduce the frequency of showing the same ad #7888
Comments
Test plan
Expected result Example of expected behavior: Ad3 Ad2 Example of broken behavior: Ad1 Ad2 Test case 1: Ads in the same child category
Test case 2: Ads in the same parent category
Test case 3: Ads in different categories (child, parent, untargeted) - triggered every 1 hour
Expected behavior: Test case 4: Ads in different categories (child, parent, untargeted) - triggered every 20 minutes
Expected behavior: |
Verification passed on
Verified test plan from #7888 (comment) Verified Test case 1 Ad AAA Ad AAA Ad BBB Verified Test case 2 Ad BBB Ad CCC Ad CCC Verified Test case 3 Encountered #8971 Hour 1 Hour 2 - fail, AD BBB not shown Hour 3 - fail, AD BBB not shown Verified passed with
AAA (Ad 1) CCC AAA
BBB (Ad 1) CCC AAA
Each ad shown was AAA as expected per the test plan
Failed due to known issue #8971 AAA (Ad 1) AAA AAA Verification passed on
Test Case 1 - FAILED Different advertised ID and creative sets Parent and child segment with diff advertiser ID and creative sets.txt
Test Case 2 - PASSED Same child category
Ads received in the 1st cycle of RR are as below: 1st cycle : 2nd cycle : Test Case 3 - PASSED Same parent category
Ads received in the 1st cycle of RR are as below: 1st cycle: 2nd cycle: |
We currently round-robin Brave Ads based upon creatives (using the catalogs
creativeInstanceId
node).To reduce the frequency of showing the same ad we should round-robin Brave Ads based upon both the advertiser (using the catalogs
advertiserId
node) and the creatives (based upon thecreativeInstanceId
).Use cases:
The text was updated successfully, but these errors were encountered: