PubNative
Features
| Bidder Code | pubnative | Prebid.org Member | yes |
|---|---|---|---|
| Media Types | display, video, native | GDPR Support | yes |
| User IDs | none | COPPA Support | yes |
"Send All Bids" Ad Server Keys
These are the bidder-specific keys that would be targeted within GAM in a Send-All-Bids scenario. GAM truncates keys to 20 characters.hb_pb_pubnative | hb_bidder_pubnative | hb_adid_pubnative |
hb_size_pubnative | hb_source_pubnative | hb_format_pubnative |
hb_cache_host_pubnat | hb_cache_id_pubnativ | hb_uuid_pubnative |
"Deal ID" Ad Server Key
hb_deal_pubnative
Registration
Before adding PubNative as a new bidder, there are 3 prerequisites:
- As a Publisher, you need to have Prebid Mobile SDK integrated.
- You need a configured Prebid Server (either self-hosted or hosted by 3rd party).
- You need to be integrated with Ad Server SDK (e.g. Mopub) or internal product which communicates with Prebid Mobile SDK.
Please see documentation for more info.
Bid Params
| Name | Scope | Description | Example | Type |
|---|---|---|---|---|
| zone_id | required | The ad zone identifier | 1 | integer |
| app_auth_token | required | The app’s authentication token | ‘aaaabbbbcccc’ | string |
Test Parameters
Please consult with our Account Manager for testing. We need to confirm that your ad request is correctly received by our system.
The following test parameters can be used to verify that Prebid Server is working properly with the Pubnative adapter.
The following json can be used to do a request to prebid server for verifying its integration with Pubnative adapter.
{
"id": "some-impression-id",
"site": {
"page": "https://good.site/url"
},
"imp": [
{
"id": "test-imp-id",
"banner": {
"format": [
{
"w": 300,
"h": 250
}
]
},
"ext": {
"pubnative": {
"zone_id": 1,
"app_auth_token": "b620e282f3c74787beedda34336a4821"
}
}
}
],
"device": {
"os": "android",
"h": 700,
"w": 375
},
"tmax": 500,
"test": 1
}