Resolver Specific Parameters (ID5 Mobile In-App)

[justadreamer]

Details

See the docs on the feature here

The gist is - add several more fields into the Targeting API call.

For ID5 Mobile In-App EID configuration, the IP passed via X-Forwarded-For will be used, and the following additional parameters are required in order to successfully return an encrypted ID5:

• bundle: Platform-specific app identifier unique to the mobile app. The bundle will be different for iOS and Android.
• ver: The mobile app’s version.
• ua: The user agent of the device’s default browser.

In addition to these required fields, the API will also accept URL parameters that may help increase resolve rates and accuracy.
id5_signature: The ID5 signature from a previous call, cached on the device or server-side. (strongly recommended)

These optional IDs should be provided using the hid field and include the appropriate Optable ID prefixes outlined here.

• i6: IPv6 address for the device
• e: Associated HEM
• p: Associated phone number
• a:  Apple IDFA  
• g: Google GAID
• c:-c9: Apple IDFV (mapped from custom ID)
• c:-c9: Publisher provided User ID (mapped from custom ID)

Testing

prebidtest tenant should have the ID5 resolver enabled, if not we'll request it.