-
Notifications
You must be signed in to change notification settings - Fork 232
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
Support for Negative Targeting in Protected Audience #896
Comments
Hello Fabrice: Would it meet your needs if we instead let negative Interest Groups filter out an entire Interest Group? Filtering individual ads from a single IG, as you propose, could be used to give that IG a lot of information. For example, your IG could contain 100 ads that each negatively-target an IG that corresponds to the user having visited a particular website. In that case generateBid could look at the whole list of non-filtered ads and learn whether or not the user had visited each of 100 different sites. Filtering out an entire Interest Group, however, works more like what you describe in your proposal: you can target ads in the normal Protected Audience way, and also you can un-target people in a negative IG. This does expand beyond the "only two sites of data" bidding model in place right now, by introduce just one bit of information from the third site where the negative IG was or was not joined. But that extra bit can only be used for filtering, and cannot be in any way bootstrapped or further combined across sites. |
Thank you for your prompt answer. This would indeed meet our needs. At InterestGroup creation time we would have an additional field in the interestGroup: This filtering would have the same treatment as a negative dot product in the process of filtering and prioritizing described here Would that be the way you see it? |
Yes! Your description matches what I had in mind. This seems like a good addition from my point of view. Heads up @orrb1, who wrote the negative targeting implementation. |
Hello, |
Hi all, I’m Jeremy, new product manager on the Protected Audience API. Our team is evaluating the negative interest group use cases, and thanks for all the valuable feedback you provided! Here we want to propose the following solutions:
With this proposal, in both contextual bids and PA bids, buyers can include multiple negative interest groups for targeting (from either the same or different origins). We look forward to your feedback on how this solution meets your needs. Thanks a lot for your feedback! |
Hello @jeremybaoty. Welcome to the funhouse, and thanks for sharing your proposal.
I'm not tracking the per bid aspect, as the proposed field is an attribute of the IG (not a renderURL). What is the interplay between Looking forward to hearing more in a Wendesday call. |
Hello Jeremy, Sorry for the late answer. We have been discussing your proposal internally and it took longer than expected. We fully agree on removing the constraint on the origin to only impose that negative Interest Groups should have the same owner as the positive ones. We would like as well to confirm that the signature mechanism with 'additionalBidKey' is not needed in this use case. Regarding the limitation to 3 negative Interest Group specified in a positive Interest Group, we do agree with that limitation. |
Hi David, Your feedback regarding the usage budget makes sense to me. I want to make some modifications the budget language here:
RE your question on updatability, an IG is allowed to do an update any time it is invited to participate in an auction — that is, any time a seller in the auction lists that IG owner as a buyer that can submit bids. This means: even when an IG is loaded but then filtered, it will be eligible for updates (subject to the IG's frequency limits). Let me know if you have additional questions! |
Got it. Thanks for clarifying @jeremybaoty. What about Fabrice's question about the key?
Perhaps we can cover it in today's call. I see there's an item for Negative targeting proposal, so I assume this issue. |
Hi @jeremybaoty, good luck in your new role! |
We fully support removing the same origin requirement for negative IGs. After some coverage analysis of advertiser use cases, we think maximum limit of 3 negative IGs per additional bid is not sufficient, can that be raised to 10 as well? That would cover the majority of use cases. |
@xxia2021 Allowing negative IGs from many domains means that a single auction's result can imply something about the user's behavior on more domains, which is a privacy problem. Why do you need so many different negative IGs for the same bid anyway? Maybe we can find another way for you to achieve the goal that does not increase the privacy leakage. |
Some advertisers just have many user segmentations to split the users into different IGs. |
I understand that, but there is no reason that each advertiser-defined user segment needs to be represented by a separate negative IG. |
@michaelkleber but an advertiser might want to suppress one product and target another. |
@eysegal The use case you're describing can be accomplished with each bid having just one negative IG, "This is an ad campaign for shirts so don't show it to the bought_a_shirt negative IG." |
@michaelkleber and when the user buys the pants but the advertiser still wants to show to socks? |
Your shirt ads would negatively target the bought-a-shirt negative IG. Your socks ads would negatively target the bought-socks negative IG. This is not a discussion about how many negative IGs exist, this is about how many different negative IGs a single bid needs to target. |
As mentioned in the Protected Audience explainer:
In online ad auctions for ad space, it’s sometimes useful to prevent showing an ad to certain audiences, a concept known as negative targeting. For example, you might not want to show a new customer advertisement to existing customers. New customer acquisition campaigns most often have this as a critical requirement.
This concept of “negative targeting” has been added to Protected Audience for bids coming from the contextual call, using “negative Interest Groups”. We propose extending it to bids based on Interest Groups.
The idea would be to have the possibility to link Negative Interest Groups to ads in « Positive Interest Groups ». An ad would then be:
{renderUrl : "url", metadata : object, negativeInterestGroups : [list of negative IG names]}
When
generateBid()
gets called, theinterestGroup.ads
object gets filtered according to the negative interest groups present on the browser for the same owner using the negativeInterestGroups attribute of ads.This mechanism would:
The text was updated successfully, but these errors were encountered: