Prebid.org Bidder Adapter Submission & Listing Assistance
Getting a bidder adapter into the Prebid.js ecosystem takes more than integration code. It needs the right tests, bidder documentation, test parameters, privacy handling, project conventions and a structured submission. DJAX Technologies helps AdTech businesses get technically ready, prepare every submission item and work through review, so your adapter is in the best position to be accepted and listed.
Most first submissions stall on the same few things.
Prebid.org accepts adapters through an open code review. Reviewers look for complete unit tests, a test ad unit that returns bids every time, a separate documentation pull request, correct consent and privacy handling, and a maintainer who answers.
Teams that build an adapter alongside their day-to-day platform work often find these items take longer than the adapter itself. Our engineers have hands-on experience preparing, submitting and maintaining Prebid adapters, and we bring that checklist to your adapter from day one.
For AdTech companies that want to be a Prebid bidder.
SSPs and DSPs
Building their own Prebid.js bidder adapter so publishers can add their demand.
Ad networks
Connecting a bidding endpoint to Prebid.js or Prebid Server for the first time.
Teams with an adapter ready
Code is written, but tests, documentation or the test endpoint still need work before submission.
Engineering teams short on time
Need experienced outside help to prepare and manage the contribution alongside their roadmap.
Teams with review feedback
A submission is open or was returned with comments that need code, test or documentation changes.
From readiness check to listing.
Seven steps, each scaled to what your adapter actually needs.
Technical readiness assessment
We review your adapter, supported media types, bidder parameters and endpoint behaviour against the current Prebid.js requirements, and give you a clear list of what is ready and what is not.
Code and implementation review
We find likely review issues in adapter conventions, request and response handling, parameters, consent and privacy signals, user syncs and other applicable requirements.
Test preparation
We review or write unit tests to the coverage the project expects, and confirm your endpoint can return stable, repeatable test bids and creatives.
Bidder documentation
We prepare the bidder documentation: supported features, parameters, consent support flags and test ad unit examples.
Submission preparation
We prepare the code and documentation pull requests to the project conventions and run the submission checklist with you.
Review-cycle assistance
We help interpret reviewer comments and make the agreed corrections until the review is complete.
Listing and handover
Once your adapter is merged into a Prebid.js release and listed, we hand over a summary of the work, open items and next steps for maintenance.
The checklist your submission has to pass.
Based on the official Prebid.js bidder adapter guide. Requirements change, so we check them again at the start of every engagement.
| Requirement | What reviewers look for | How we help |
|---|---|---|
| Unit tests and coverage | Every adapter needs unit tests; pull requests are expected to reach the project coverage bar. | We review or write the tests and check coverage before submission. |
| A test ad unit that always bids | Reviewers check that test parameters return bids and creatives consistently. | We confirm your endpoint and test parameters behave the same way every time. |
| Documentation pull request | A separate docs pull request describes the bidder, its parameters and the features it supports. | We draft it with you and keep it in step with the code. |
| Consent and privacy signals | TCF (with your GVL ID), GPP, US privacy and COPPA signals must be passed through correctly. | We review the signal handling and the matching documentation flags. |
| Project conventions | All code lives in the adapter, network calls only where allowed, user syncs registered the standard way, bidder code rules followed. | We check the adapter against the current module rules. |
| A responsive maintainer | Each adapter names a maintainer email that answers reviewer and publisher questions. | We help you set up the maintainer contact and the handover so it stays responsive. |
How an engagement runs.
- Assess
- Prepare
- Test
- Document
- Submit
- Respond to review
- Listing and handover
How much work each stage takes depends on how mature your adapter is and on the requirements that apply to it. The readiness assessment tells you exactly that before any further work is agreed.
Prebid.js and Prebid Server
In-app demand reaches bidders through Prebid Server, so many bidders need both adapters. We cover the Prebid.js adapter and, when you need it, the Prebid Server adapter in Go, followed by the Java port.
Need an adapter built from the start?
If you do not have an adapter yet, see our Prebid adapter and module development service. We build it, then take it through the same submission and listing process. See adapter development →
Clear scope before any work starts.
Every engagement starts with a short readiness review. You then receive a clear, fixed scope and quote before any further work begins, with no open-ended hourly billing. Anything outside that scope is agreed with you in writing first.
Included
- Readiness assessment of your adapter and endpoint
- Review of existing adapter code and structure
- Review or preparation of tests and documentation
- Submission preparation and guidance
- Support through the review cycle for the agreed scope
- Handover once the adapter is listed
Scoped and quoted separately
- Building a complete adapter from scratch
- Major redesign or rewrite of an existing adapter
- Changes to your bidder endpoint or backend
- New test infrastructure on your side
- Prebid Server adapter development
- Extra media types such as native or CTV, unless agreed
- Google Ad Manager setup and validation
About Prebid.org review and listing
DJAX Technologies provides technical preparation and submission assistance. Prebid.org reviews every contribution independently and makes the final decision on acceptance and listing. We prepare each adapter to meet the applicable technical requirements, tests, documentation and reviewer feedback, so that it is ready to be accepted and listed. Review time, bidder code availability and the release in which an adapter appears are decided by the project. Progress also depends on your endpoint readiness, test responses and responsiveness during review. DJAX is not affiliated with or endorsed by Prebid.org.
Your adapter, your listing.
You stay the owner
The adapter, the bidder code and the listing are yours. Your company remains the maintainer named in the project.
We work in your repository
We work in your fork or under your GitHub organisation, so the history and the pull requests stay with you.
A maintainer contact that answers
We help you set up a group email for the maintainer role, so reviewer and publisher questions keep getting answered after handover.
Running Revive Adserver?
If you want your Revive ad server to take part in Prebid auctions as a bidder, a ready-made bidder adapter for Revive Adserver is available from our Revive plugin store. This service is different: it is for companies that already have their own bidding endpoint and adapter, on any platform. See the Revive bidder adapter →
Common questions
Is Prebid.org membership required to get an adapter listed?
No. Prebid.org accepts bidder adapters through an open code review. Membership is optional.
Can you guarantee acceptance or a listing date?
No one can. Prebid.org reviews every contribution independently and releases on its own schedule. We prepare your adapter so it meets the requirements and handle the review with you, which puts it in the best position to be accepted and listed.
Who submits the pull requests?
The pull requests come from your repository or your fork, with your company named as maintainer. We prepare them and can open them with you or on your behalf.
Do you handle Prebid Server adapters too?
Yes. We can review, prepare or build Prebid Server adapters in Go and Java. Building one is scoped separately.
What do you need from us to start?
Access to your adapter code if you have it, your bidder endpoint details, the media types you support, and any earlier review feedback. The enquiry form asks for these.
We already submitted and got review comments. Can you help?
Yes. Send us the pull request link and the comments. We assess what is needed and help you resolve them.
How do you price this work?
After a short readiness review we agree a fixed scope and quote for the work your adapter actually needs, before anything further starts.
Get your adapter ready for submission and listing.
Tell us where your adapter stands. We will reply with what it needs and how we would approach it.