-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Reduced delivery of Brave ads campaigns with subdivision targeting #18748
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
Labels
bug
feature/ads
OS/Desktop
OS/iOS
Fixes related to iOS browser functionality
priority/P1
A very extremely bad problem. We might push a hotfix for it.
QA Pass-Linux
QA/Yes
release-notes/exclude
Milestone
Comments
This was referenced Oct 15, 2021
Closed
Verification passed on
Full test run on 1.33.x can be found in brave/brave-core#10551 (comment) 1st ad US-CA
2nd ad US-OR
3rd ad US-CA after round robin
4th US-OR after round robin
5th US-CA
6th US-OR
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
feature/ads
OS/Desktop
OS/iOS
Fixes related to iOS browser functionality
priority/P1
A very extremely bad problem. We might push a hotfix for it.
QA Pass-Linux
QA/Yes
release-notes/exclude
Description
Reduced delivery of Brave ads campaigns with subdivision targeting
Steps to Reproduce
Actual result:
Ads/advertisers do not round robin if a campaign has state level targeting for another state
Expected result:
Ads/advertisers should round robin if a campaign has state level targeting for another state
Reproduces how often:
Easily reproduced
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
Round robin does not work if ads are excluded due to state level targeting. This will also help with high CPU usage as a user will not be stuck in the state where there are no ads. And if they are, follow up performance fixes are being worked on
The text was updated successfully, but these errors were encountered: