-
Notifications
You must be signed in to change notification settings - Fork 216
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
Intent vs Interest Groups #13
Comments
The interest group name is picked by the advertiser, and then the name is used by someone buying on behalf of that same advertiser to place their ad. So for the example illustrated in that sample URL, WeReallyLikeShoes.com has an account with In particular, note that interest group memberships are hidden from programmatic buyers unless the advertiser has specifically chosen to reveal them to a buyer, with whom they presumably have a relationship. Check out the brief mentions of encryption for how the interest group membership can pass through the supply chain and be opaque to anyone other than the intended buyers — but the details there ought to be worked out by the ad industry, not by browsers. |
Thanks for the prompt response. So in the example it makes sense to me when wereallylikeshoes.com is trying to re-target its own pre-existing visitors. What is still unclear to me is how does the user receive ads from similar advertisers which it hasn't come in to contact with say welikeothershoes.com ? Or more simply put - how did the user discover wereallylikeshoes.com in the first place? |
Too add to this - in re-reading the example about the use of "cross-domain iframes" allowing third party sites to create interest groups I think I can back in to this and answer my own question. I suppose then the question becomes do ad networks or DMPs request publishers to place "cross-domain iframes" to create ad network wide interest groups in the same way they ask publisher to place cookie sync pixels today? |
Yes, the "cross-domain iframe" paragraph in the Joining Interest Groups section seems like the kind of thing you're asking for. It's worth noting that browsers are likely to provide UI controls that show information like "What site was I visiting when I got added to this interest group?" So if WeReallyLikeShoes and their ad network do as you suggest, then a person wondering about that ad for othershoes.com could see that "OtherAdNetwork added you to their interest group 'shoes-123' while you were visiting WeReallyLikeShoes.com last Tuesday." |
Thanks for clarifying. |
Interesting stuff.
In the "motivating use case" section it reads to me that it is assumed that the ad network will somehow be able to translate
GET https://first-ad-network.com/.well-known/fetch-ads?interest_group=www.wereallylikeshoes.com_athletic-shoes
into an intent signal in order to place a bid. Is this indeed the case?If so, would this require those setting the interest group to use highly effective naming conventions so that the ad network could indeed determine the intent signal associated with this group. In other words if in this example the group that was set was to be called "item323442" instead of "www.wereallylikeshoes.com_athletic-shoes" the group name would likely be meaningless to a programmatic group of buyers who didn't exactly know they were looking to target something called "item323442" but instead were looking to target just "athletic shoes".
If my assumption here is completely wrong - could you provide some additional clarity as to how intent based targeting will work within the turtledove environment?
The text was updated successfully, but these errors were encountered: