Trust and Supply Quality
CloudX public controls for publisher eligibility, traffic integrity, brand safety, creative quality, and measurement.
This page separates the controls buyers can rely on from metrics that require dated evidence. It summarizes the public CloudX contract; it does not claim that every impression is viewable or free of invalid traffic.
Control summary
| Area | Public control |
|---|---|
| Publisher eligibility | The Publisher Policy excludes fraudulent, non-production, predominantly advertising, low-quality automatically generated, and significantly unmoderated user-generated properties. |
| Traffic integrity | Publishers may not generate automated or non-human ad interactions, inflate impressions or clicks, or forward requests from third-party properties. |
| Auction execution | Supported rounds can rank bids inside an isolated, attestable Trusted Execution Environment. Its evidence covers enclave execution, not bidder solicitation, rendering, billing, or IVT. |
| Supply path | CloudX-settled requests use one seller ID in app.publisher.id, the CloudX schain node’s sid, and CloudX sellers.json. Buyers must separately verify publisher-hosted app-ads.txt, which can be missing or stale. |
| Publisher blocks | Requests carry configured bcat and badv values. CloudX rejects bids whose declared category or advertiser domain matches them. |
| Demand content | The Demand Partner Policy defines prohibited and restricted content and requires compliance with CloudX creative specifications. |
| Creative behavior | The CloudX renderer rejects unsupported or unparseable creatives and preserves an SDK-owned close control on fullscreen ads. |
| Viewability | The CloudX SDK attempts OM SDK sessions for supported CloudX-rendered HTML and VAST; active IAB registry entries exist, but shipped-version parity must be validated. |
| AI and MFA risk | Predominantly advertising or low-quality automatically generated properties are ineligible; AI-generated ads must carry legally required labels. |
| Enforcement | CloudX may block or limit ads, suspend or terminate access, and withhold or terminate payments under its policies and agreements. |
Supply and traffic integrity
The Publisher Policy is the eligibility baseline. It prohibits:
- Automated, inauthentic, or non-human ad interactions
- Artificial inflation of impressions, clicks, conversions, or cost
- Fraudulent traffic and properties built primarily to send outbound traffic
- Properties that are predominantly ads rather than original publisher content
- Low-quality automatically generated content without meaningful engagement
- Forwarding ad requests from a third-party property
Supply Transparency explains how to verify the publisher account on each CloudX-settled request. Authorization is one quality signal; it does not replace your own invalid-traffic controls.
Brand safety and creative quality
Publishers can configure IAB category and advertiser-domain blocks. CloudX sends them as bcat and badv and rejects a bid when the bid’s declared cat or adomain matches the applicable block list.
Demand partners must follow the Demand Partner Policy, including its prohibited-content, restricted-content, privacy, malware, deceptive-design, and child-safety rules. bid.adomain is required and must be accurate. bid.cat is recommended and must be accurate when supplied; missing or inaccurate categories limit bcat enforcement.
CloudX-rendered creatives must also pass the Creative Specification. Unsupported VAST, unparseable markup, or a creative-type mismatch fails the render and reports an error; another creative from the same auction is not guaranteed.
Measurement scope
CloudX has active Android and iOS entries as Cloudxai in the IAB Tech Lab OM SDK compliance program. Certification coverage is version-specific; confirm the shipped SDK version against the current registry entry before relying on certified coverage. Viewability documents supported formats and best-effort runtime behavior.
OM SDK integration establishes an intended measurement capability that must be validated against the shipped version. It does not establish:
- A 100% viewability rate
- A guarantee that every creative includes a valid verification resource
- Measurement for demand rendered by a separate partner SDK
- An independent invalid-traffic determination
Evidence boundaries
CloudX does not publish a timeless IVT rate, MFA rate, viewability rate, incident count, vendor roster, or publisher ranking in developer docs. Those values depend on the measurement vendor, definition, inventory slice, and time window.
For due diligence, request a dated evidence pack that names:
- The metric definition and measurement vendor
- Included formats, regions, and publishers
- Observation window and sample size
- Invalid-traffic and viewability methodology
- Known exclusions and limitations
Report a concern
- Technical or supply-path issue:
support@cloudx.io - Policy, privacy, or content concern:
legal@cloudx.io
Include the request id, impression id, timestamp, app bundle, seller ID, and the reason for escalation. Do not include raw personal data or credentials.