Demand Changelog

Publisher network and OpenRTB buyer integration release history

2026-09-02

Intent IQ passthrough

CloudX now forwards publisher-provided Intent IQ IDs under intentiq.com with atype: 1.

Publishers pass the ID with setUserKeyValue("intentiq.com", id); no SDK update is required.
CloudX passes the ID unchanged and does not run Intent IQ server-side resolution. Demand partners activate intentiq.com IDs through an Intent IQ partnership.

2026-08-21

EUID passthrough

CloudX now forwards publisher-provided EUID advertising tokens under euid.eu. EUID is the European counterpart to UID2 and uses atype: 3.

Publishers pass the advertising token with setUserKeyValue("euid.eu", token); no SDK update is required.
CloudX passes the token unchanged. Authorized demand partners decrypt it through their EUID bidstream integration.

Read the extended identifier docs →

2026-08-20

Extended identifiers

CloudX now forwards publisher-provided UID 2.0, LiveRamp, and ID5 values on bid requests. Publishers pass them with the existing setUserKeyValue API; no SDK update is required.

Publisher keys are uidapi.com (UID2 advertising token), liveramp.com (LiveRamp ATS envelope, not a RampID), and id5-sync.com (ID5 universal UID).
OpenRTB 2.6 bidders read user.eids. OpenRTB 2.5 bidders read user.ext.eids.
CloudX does not generate, decrypt, or replace these values and does not run LiveRamp Sidecar.

Publisher setup: Android, iOS, Unity, React Native, and Flutter

Demand partner setup: Read the extended identifier docs →

2026-07-28

zstd bid compression

CloudX now supports zstd compression for OpenRTB traffic with demand partners, on both bid requests and bid responses.

Bid requests can be sent with Content-Encoding: zstd; gzip remains supported.
When CloudX advertises Accept-Encoding: gzip, zstd, partners may respond with gzip or zstd.
Contact CloudX to enable zstd for your bidder endpoint.

Read the docs →