Skip to main content
CloudX connects demand partners to publisher inventory through the CloudX exchange over OpenRTB. Depending on your integration model, winning creatives are rendered either by your own network SDK or directly by CloudX.

​
Integration models

SDK bidder

Your network SDK is embedded in the publisher app via a CloudX adapter. Your SDK loads and renders the creative; CloudX orchestrates the auction and lifecycle. CloudX does not render it.

Server-to-server (SDK-less)

You respond to CloudX bid requests over OpenRTB with creative markup in bid.adm. There is no network SDK in the app — CloudX renders the creative directly. This is the path the CloudX-Rendered Creative Specification governs.

​
When CloudX renders your creative

For server-to-server demand, a bid is rendered by the CloudX SDK when the bid response carries the render provider marker: 
{
  "ext": {
    "cloudx": {
      "render": { "provider": "cloudx" }
    }
  }
}
When provider is cloudx, the CloudX SDK renders the creative in-app from bid.adm, regardless of which demand partner supplied the bid. When the marker is absent, rendering is delegated to a network SDK.
If your creatives are rendered by CloudX, read the CloudX-Rendered Creative Specification for the accepted creative types, supported formats, per-bid configuration, and user-experience behavior.

​
Getting started

Server-to-server integrations are provisioned per partner (bid endpoint, credentials, and creative review). Contact your CloudX partner manager to begin an integration.