Supported Demand Partners
How CloudX auctions work and how to set up each demand partner.
CloudX brings SDK partners and server-side buyers into one auction for every ad request. Start with the flow, then choose the setup that matches your integration.
Add demand to your app
Choose an SDK or SDK-less partner, then follow its setup guide.
Connect an OpenRTB endpoint
Review endpoint onboarding, timeouts, and outcome notifications.
How an ad request works
1. Collect bids
Adapters gather SDK-side bids or bid tokens. The CloudX SDK sends them with one ad request to the auction server.
2. Run the auction
Each round calls its eligible bidders in parallel. CloudX applies any applicable bid adjustments and the round’s price floor, then ranks valid bids. The highest adjusted bid wins; ties are random. For supported integrations, ranking can run inside a Trusted Execution Environment that produces verifiable evidence.
3. Show the ad
The first round with a valid bid ends the auction. The partner SDK or CloudX renderer then shows the winning ad.
If no round returns a valid bid, the request is unfilled. Line items control which bidders enter each round, the round order, and price floors.
Explore auction rules and examples
See rounds, priorities, price floors, and interactive auction simulators.
Choose the right setup path
An adapter connects the partner SDK to the CloudX SDK.
CloudX calls the bidder server-to-server and renders its winning creative. No partner SDK or adapter is required.
- Open the partner’s publisher guide in the directory.
- Enable the bidder and add it to the relevant line items.
- Keep using your standard CloudX SDK integration.
Partner directory
Partner availability varies by account. Contact your CloudX account manager if a partner is not available in your dashboard.
SDK partners
| Partner | Publisher setup | Adapter setup |
|---|---|---|
| BIGO Ads | Guide | Android |
| Digital Turbine | Guide | Android, iOS, Unity |
| Google AdMob / GAM estimated | Guide | Android, iOS, Unity |
| InMobi | Guide | Android, iOS, Unity |
| Magnite | Guide | Android, iOS, Unity |
| Meta Audience Network | Guide | Android, iOS, Unity |
| Mintegral | Guide | Android, iOS, Unity |
| MobileFuse | Guide | Android, iOS, Unity |
| Moloco | Account manager | Android, iOS, Unity |
| Pangle | Account manager | Android, iOS, Unity |
| TaurusX | Account manager | Android, iOS, Unity |
| Unity Ads | Guide | Android, iOS, Unity |
| Verve | Account manager | Android, iOS, Unity |
| Vungle / Liftoff Monetize | Guide | Android, iOS, Unity |
SDK-less partners
No adapter is required.
OpenRTB buyers
Contact your CloudX account manager to onboard an OpenRTB 2.5 or 2.6 endpoint. Start with Buyer Onboarding, then review the OpenRTB reference before testing.
Respond within the tmax timeout specified on each request. Return standard OpenRTB notification URLs on your bids. Delivery is asynchronous and not exactly once, so make handlers idempotent.