what about geo targeting?

[fregas]

One thing I haven't seen in either TURTLEDOV or this proposal is a way to geotarget? Currently, we get lat/lng from the bid stream, and since we have unique IDs (cookies, or more likely IDFAs) then we can target that same user and also do in store conversion attribution.

Is there any way to target based on approximate lat/lng with either proposal?

[michaelkleber]

In TURTLEDOVE, the contextual request could still come with whatever geo information is available, e.g. coarse-grained IPGeo. (Just the current one, not any history.)

In a context where first-party information remains available (e.g. news-site.com decides it's OK sending its first-party user ID into the auction), you could build up single-site-only info over time. Or the first party could do it for you, and send the targeting hint "I want an ad for a visitor of news-site.com who was in Paris last month", if you have such an arrangement.

But you wouldn't be able to associated an ad request with a cross-site geo history.

[BasileLeparmentier]

It is also possible I guess to have interest group that are linked to a geo, isn't it possible Michael?
As long as this interest group is created via aggregation and that it fits privacy criteria, it should be possible to use it.
This is one of the example I put for meta interest groups potential usage in this page https://github.com/BasileLeparmentier/SPARROW/blob/master/Interest_groups_audiences_new_building_blocks.md

[michaelkleber]

Ah true, every time you see someone in Paris, you could add them to your interest group "People in Paris in the past month", with 30-day expiration.