Carrier Name and App Categories mapping about openrtb-doubleclick HOT 3 CLOSED

Not sure about using that to map the OpenRTB field. The problem is that the OpenRTB spec requires MNC codes, but our CSV doesn't include that... outside the US this gets messier, you need two codes (MCC + MNC) unless I map only the MNC and assume that users will use that as a compound key with the country from geo info. (And I wouldn't bet there's a 1:1 relationship of country:MCC.) Anyway AdX doesn't provide either MCCs or MNCs anywhere in the protocol or mapping files. But it makes sense to have this CSV loaded by DoubleClickMetadata to help users that don't want to deal with Google's carrier IDs.

Mobile app categories are a harder problem, we don't yet have a mapping table from the Google Play categories to IAB, this may take more time... the spreadsheet was filled in a bit optimistically for this field, for now I'm annotating it to make clear this is planned by not implemented yet.

from openrtb-doubleclick.

Check out e1ca649

from openrtb-doubleclick.

I've reviewed the OpenRTB spec and it says this about carriers:

carrier - string - Carrier or ISP (e.g., “VERIZON”). “WIFI” is often used in mobile to indicate high bandwidth (e.g., video friendly vs. cellular).

I agree that MNC + MCC code would be the best way to inform about the carrier, but in the meantime I think it's nearer to the standard to have the carrier name instead of the google carrier ID.

Thank you very much for the changes!

from openrtb-doubleclick.