-
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
Follow up to #6253: Automatically limit unwanted Brave Ads delivery #11617
Comments
Verification passed on
Verified test plan from https://github.com/brave/internal/issues/719#issue-696145308 Verified Limit landed ad - Untargated - 1 Campaign, 1 CreativeSet, 2 Ad
Verified unable to see the ad after 47 hours.
Verified Release landed ad - Untargated - 1 Campaign, 1 CreativeSet, 2 Ad
Verified Limit landed ad - Untargated - 1 Campaign, 2 CreativeSet, 1 Ad
Verified unable to see the ad after 47 hours.
Verified Limit landed ad - Untargated - 2 Campaign, 1 CreativeSet, 1 Ad
Verified ad from other campaign is shown
Verified ad from landed campaign are not shown and ads from the other campaign are shown
Verified Limit landed ad - Parent only - 1 Campaign, 2 CreativeSet, 1 Ad
Verified unable to see the ad after 47 hours.
Verified Limit landed ad - Parent-Child - 1 Campaign, 2 CreativeSet, 1 Ad
Verified unable to see the ad after 47 hours.
Verified Limit ads dismissed in a row
Verified ad was dismissed the second time
Verified unable to see the ad after 47 hours.
Verified Release dismissed ads
Verified passed with
Verified test plan from https://github.com/brave/internal/issues/719 Limit landed ad - Untargated - 1 Campaign, 1 CreativeSet, 2 AdVerified ad landed:
Verified unable to see the ad after 47 hours
Release landed ad - Untargated - 1 Campaign, 1 CreativeSet, 2 AdVerified ad is shown:
Limit landed ad - Untargated - 1 Campaign, 2 CreativeSet, 1 AdVerified ad is landed:
Verified unable to see the ad after 47 hours:
Limit landed ad - Untargated - 2 Campaign, 1 CreativeSet, 1 AdVerified ad has landed:
Verified ad from other campaign is shown:
Verified ad from landed campaign are not shown and ads from the other campaign are shown:
Limit landed ad - Parent only - 1 Campaign, 2 CreativeSet, 1 AdVerified ad has landed:
Verified unable to see the ad after 47 hours:
Limit landed ad - Parent-Child - 1 Campaign, 2 CreativeSet, 1 AdVerified ad has landed:
Verified unable to see the ad after 47 hours:
Limit ads dismissed in a rowVerified ad was dismissed:
Verified ad was dismissed the second time:
Verified unable to see the ad after 47 hours:
Release dismissed adsVerified ad is shown:
Verification passed on
Verified Limit landed ad - Untargated - 1 Campaign, 1 CreativeSet, 2 Ad
Verified unable to see the ad after 47 hours.
Verified Release landed ad - Untargated - 1 Campaign, 1 CreativeSet, 2 Ad
Verified Limit landed ad - Untargated - 1 Campaign, 2 CreativeSet, 1 Ad
Verified unable to see the ad after 47 hours.
Verified Limit landed ad - Untargated - 2 Campaign, 1 CreativeSet, 1 Ad Verified ad has landed
Verified ad from other campaign is shown
Verified ad from landed campaign are not shown and ads from the other campaign are shown
Verified Limit landed ad - Parent only - 1 Campaign, 2 CreativeSet, 1 Ad
Verified unable to see the ad after 47 hours.
Verified Limit landed ad - Parent-Child - 1 Campaign, 2 CreativeSet, 1 Ad
Verified unable to see the ad after 47 hours.
Verified Limit ads dismissed in a row
Verified ad was dismissed the second time
Verified unable to see the ad after 47 hours.
Verified Release dismissed ads
|
Follow up to #6253. The issue is still reproducible.
Description
While we currently have a feedback tool for ads which will limit delivery of downvoted ads, there have been many requests to limit delivery of repetitive ads so that the out of the box user experience is better. Eventually this will be handled by contextual "bandits" but in the mean time, we need some simple rules to help improve the situation.
The proposed rules are as follows
Test plan
https://github.com/brave/internal/issues/719
The text was updated successfully, but these errors were encountered: