As publisher I would like to pass geo information to prebid server

[jevansnyc]

As a partner such as a CMP for consent, or an SSP or DSP who are selling and buying impression opportunities, we need to accurately communicate one or more of the following:

• Country (required)
• Region (required)
• City
• DMA (metro-code in Fastly)

and potentially other data that are available for geo-targeting or consent requirements.

We currently collect this in common - src - constants.rs and I think this is fine for now, but we must consider that not all edge cloud platforms will have the same geo information available in the request.

For the time being, lets ensure that at least the 3 fields above are passed in appropriate headers as such:

pub const HEADER_X_GEO_CITY: HeaderName = HeaderName::from_static("x-geo-city");
pub const HEADER_X_GEO_COUNTRY: HeaderName = HeaderName::from_static("x-geo-country");
pub const HEADER_X_GEO_METRO_CODE: HeaderName = HeaderName::from_static("x-geo-metro-code");
pub const HEADER_X_GEO_REGION: HeaderName = HeaderName::from_static("x-geo-region");

Pass geo information to prebid within device properties

Please ask questions if this isn't clear.

[ChristianPavilonis]

I see that we're already getting geo info (from fastly) in geo.rs (except region).
When geo::get_dma_code() is called the headers do get set.

Where do I need to pass the geo info to?
I see there's a todo comment to add geo info if available in prebid_proxy.rs
Does google ad manager need it?

For Didomi are you suggesting to rewrite the script like in the html_processor.rs? or developers just use our headers?

[therevoltingx]

BTW, DSPs/SSPs read the go information from within the OpenRTB request. Not sure about Prebid but we should probably format it in a way that they can read.