The full onboarding process of a new bidder to PubNative's platform takes up to a week, but with the collaboration of the DSP it can take only a few days.
Integration
Please follow the following guidelines while integrating the PubNative spec. Our spec is based on OpenRTB specifications, and the following information details about specs as well as recommended best practices.
Specification
PubNative Exchange allows a mechanism for DSPs and advertisers to bid at an impression level in a standard second price auction model (the winning bid will pay the second highest price in the auction). PubNative specification aligns with OpenRTB 2.3 specifications and may be upgraded to adhere to the newest versions of OpenRTB specs if there are substantial modifications. While we try to adhere to OpenRTB 2.3 to the extent possible, we may require some exchange specific requirements that are optional in the OpenRTB spec, in order to ensure the best buying and selling environment for our DSPs and publishers.
Pubnative OpenRTB 2.3 spec
Please refer to the Technical Integration section for further details and explanations on our spec and contact [email protected] if you have any questions.
Onboarding process:
Integration
To get started with PubNative, please sign the MNDA, contract and the evaluation form. Please also provide at least two credit references for our finance team. Once completed, please complete integration using the steps below:
- Build your bidder to comply with the PubNative OpenRTB 2.3 spec and OpenRTB Native V 1.1 spec.
- To verify that the bid response is valid, please copy/paste the text of a valid and complete bid response from your bidder, save to a txt file, and email directly to your integrations lead.
- Upon confirming the bid response, we will schedule a 30 min integration call with your team. One member from your tech and ad ops team should be present and the time will be used to answer any questions you have.
Complete PubNative Spend Consent Form. - Impressions confirmation window on PN ad server is 1hour. So we recommend DSP to have the same on their end to avoid discrepancies. In case of any questions please contact your Account Manager
Testing
- Create a new test endpoint
- Your endpoint will be capped at a maximum of 5% QPS for testing
- Go live on both iOS and Android campaigns.
- IMPORTANT: Cap spend on your end at $100 max, in order to avoid overspend due to integration issues.
- While this is a “testing” period, it is live traffic. You will be placing bids and winning inventory on real publisher inventory., so you will be billed for the impressions won during testing as well.
Comparing reports
- Compare reporting to the data generated from nurl and/or imptrackers (based on your reporting parameter) and verify that reporting is less than 10% discrepant. When you pull reporting, please make sure to send them in UTC.
- Once reporting alignment is complete, your integrations lead will work with you to customize your bidder setup. Let us know which countries you would like to receive inventory from and whether you have a max QPS your infrastructure can support. The average traffic on the PubNative exchange is currently 2500 QPS for native ads.
- After customized set up is verified and complete, your integrations AM will turn you live on RTB 2.3 with the endpoint of your choice.
- One week post-integration, we will do a check-in to review the integration and evaluate how to optimize your account.
- For the first billing cycle, please send tax documents as asked by your account team.