Supply Transparency

How buyers verify CloudX publisher inventory across app-ads.txt, sellers.json, and OpenRTB schain.

For CloudX-settled requests, one publisher seller ID connects three IAB transparency sources: the publisher’s app-ads.txt file, CloudX’s sellers.json, and the request’s SupplyChain object.

Check app-ads.txt

Find cloudx.io, <seller_id>, DIRECT.

Check sellers.json

Find the same value in seller_id.

Check OpenRTB schain

Match it to the CloudX node’s sid.

The matching rule

On a request with imp.ext.cloudx.settlement: "cloudx":

SourceExpected value
app.publisher.idThe publisher’s CloudX seller ID
CloudX schain node asicloudx.io
CloudX schain node sidSame value as app.publisher.id
CloudX schain node ridSame value as the top-level request id
CloudX schain node hp1
schain complete1
CloudX sellers.json seller_idSame value as app.publisher.id
Publisher app-ads.txtcloudx.io, <app.publisher.id>, DIRECT

OpenRTB 2.6 places the object at source.schain. OpenRTB 2.5 places it at source.ext.schain.

The Demand Partner Policy requires you to pass schain accurately and completely, without stripping, truncating, spoofing, or otherwise misrepresenting it. Preserving schain does not authorize reselling, re-routing, or re-broadcasting CloudX bid requests; obtain CloudX’s prior written permission for any such redistribution, including routing a request back into CloudX through a separate seller integration. See Bid request handling.

{
  "id": "auction-123",
  "app": {
    "publisher": { "id": "publisher-456" }
  },
  "imp": [{
    "ext": {
      "cloudx": { "settlement": "cloudx" }
    }
  }],
  "source": {
    "schain": {
      "complete": 1,
      "ver": "1.0",
      "nodes": [{
        "asi": "cloudx.io",
        "sid": "publisher-456",
        "rid": "auction-123",
        "hp": 1
      }]
    }
  }
}

Verify a request

  1. Confirm imp.ext.cloudx.settlement is "cloudx".
  2. Read app.publisher.id and the CloudX schain node.
  3. Find that seller ID in CloudX sellers.json.
  4. Resolve the app’s developer domain from its store listing and verify its public app-ads.txt contains the matching CloudX DIRECT line.

Direct and resold lines

DIRECT means the publisher has a direct account relationship with the advertising system named in that line. CloudX’s own authorization line uses cloudx.io and the publisher’s CloudX seller ID.

A publisher can also have lines for other demand systems. Those systems decide whether their line is DIRECT or RESELLER; that relationship does not change the meaning of the CloudX line. Evaluate each advertising-system domain independently.

Publication controls

CloudX sellers.json:

  • Lists enabled publisher accounts with a name and domain
  • Publishes them as seller_type: "PUBLISHER"
  • Publishes seller identities with is_confidential: 0
  • Publishes cloudx.io in the sellers.json TAG-ID identifier field; this is not a TAG certification claim

CloudX flags missing or stale app-ads.txt lines to publishers. Buyers should still crawl the publisher’s file on their own schedule.

Seller records show authorization, not current availability, traffic volume, exclusivity, or quality metrics. Obtain dated inventory data separately.