Become a Certified Adapter

All new partners must complete the certification process before becoming a bidder in the Header Tag Wrapper. Certification is an eight-step process:

The workflow steps included in this topic, displayed as arrows

Complete the following steps to become a certified adapter:

  1. Reach out to us. Contact 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.
  2. 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.
  3. Complete our documents. Complete the new partner questionnaire and our integration agreement. You'll need to attach the completed integration agreement to your New Adapter Certification ticket (which you'll log in step 4).
  4. Note: We recommend reading our Header Tag Wrapper documentation to learn more about the product you’ll be integrating with.
  5. 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.
  6. When you're finished, confirm you've met our adapter code submission guidelines, then log a pull request in GitHub against the master Branch.
  7. Log a New Adapter Certification ticket. In our external service desk, log a New Adapter Certification ticket.
  8. Need help setting up an account or logging the ticket? See External Service Desk for Partners.
  9. Review, revise, repeat. The review cycle begins when we receive your pull request. A few things happen during the review cycle:
    1. We’ll review your code to make sure it’s compatible with our technology. In most cases, we’ll reach out and ask you to make a few changes.
    2. Make the code changes in your GIT repository then log another pull request.
    3. We’ll review your code again and let you know if we have any additional changes.
    4. We test your adapter when we’re satisfied with the code, but may reach out to request more changes, depending on the results achieved in testing.
  10. 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.
  11. 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.
  12. Note: If you’re a publisher who initiated the adapter certification process, you’ll be included in the alpha testing.
  13. 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.
  14. We may reach out to you for changes if any performance issues are flagged.
  15. Congrats, you’re officially certified! If everything looks good during the validation, we build you into our IX app. Welcome to the team!