All new partners must complete the certification process before becoming a bidder in the Header Tag Wrapper. Certification is an eight-step process:
Complete the following steps to become a certified adapter:
Reach out to us. Contact firstname.lastname@example.org and indicate that you want to become an adapter in the Header Tag Wrapper. We’ll get in touch to help you set up your GitHub repository. To do this, we'll need you to provide a list of names and email addresses of everyone on your team who requires access to it. We’ll create their accounts and send you the login credentials
If you’re a publisher who wants to request the inclusion of a partner you’re already working with, indicate the name of the company and provide contact information so we can communicate with the partner directly.
Build your adapter. Log in to GitHub and fork the ht-wrapper-adapters repository. Follow the instructions inside the repo to setup, develop, and test your adapter. Reach out to us if you have any questions; we’re happy to provide guidance.
When you're finished, confirm you've met our adapter code submission guidelines, then log a pull request in GitHub against the master Branch.
Log a New Adapter Certification ticket. In our external service desk, log a New Adapter Certification ticket.
Need help setting up an account or logging the ticket? Check out our External Service Desk for Partners help topic.
Review, revise, repeat. The review cycle begins when we receive your pull request. A few things happen during the review cycle:
The review and revision stages may cycle a few times and it may seem like we’re suggesting a lot of changes. But don’t worry: it’s only to ensure your adapter’s success in a production environment.
Recruit publishers for alpha testing. When we’re both satisfied with the test results, we merge your code to production and begin alpha testing. Provide us with a list of publishers who can test your adapter in a production environment.
Code validation. During the alpha testing, we’ll review your adapter together to see how it’s performing. We’ll check that bid requests are sent, bid responses are received, ads are being rendered successfully, and accurate reporting statistics are available in Wrapper Pulse. If everything looks good, we’ll reach out to the publishers participating in the alpha testing to confirm they’re satisfied with your adapter’s performance as well.
We may reach out to you for changes if any performance issues are flagged.
Congrats, you’re officially certified! If everything looks good during the validation, we build you into our UI. Welcome to the team!