Launch checklist

Agree before integration

Confirm SSP / DSP identity, endpoints, OpenRTB version, formats, App / Site sources, and test scope.
Exchange credentials through an agreed secure channel, not browser forms, public repositories, logs, or chat.
SSP: confirm audience, SSP ID, key ID, clock synchronization, and rotation expiry. DSP: explicitly choose none / bearer / header.
Agree request and response budgets, traffic limits, and an incident channel. Implementation defaults are not a production SLA.

SSP checks

Verify eight-field LF joining, no trailing LF, 32-byte Base64 decoding, and 64-character lowercase hexadecimal signatures against the public vector.
With real test credentials, verify success, incorrect key / audience / path, time-window boundaries, duplicate headers, duplicate nonce, and rotation.
Confirm proxy path preservation, no query, one JSON Content-Type, and no compression. Do not rely on HMAC to protect the body.
Check one impression, explicit at=1, USD, mutually exclusive App / Site, country / OS / Bundle dimensions, and request-size limits.
Cover 200, 204, 401, 409, 413, 415, 429, and 503. Clients must not parse empty error bodies as JSON.
Use fresh time and nonce on retries, and separately handle business duplication of auctions, impressions, and notifications.

DSP and creative checks

Verify certificate validation, version headers, and configured authentication on the actual HTTPS connection; SSP authentication must not be forwarded.
Return timely uncompressed 200 JSON or 204. Cover late replies, error status, bad JSON, oversized bodies, and an invalid individual bid.
Correlate request.id and impid exactly; use USD with positive gross bids and verify floors, margin, and net output.
Render Banner HTML, Video VAST, and Native assets in real clients. Pass-through fields do not mean G24ad has verified player, media, or privacy capabilities.
Test bcat / badv / bapp / battr and seat restrictions; provide required creative identity and verify blocked creatives do not win.
Confirm ${AUCTION_PRICE} is DSP gross in six-decimal USD CPM while outer bid.price is SSP net.

Notifications and rollout

Agree actual win / bill / loss event semantics, the notification executor, and other macros. ADX does not send these callbacks.
Account for receiving only the winning bid, not all losing DSP notifications. Do not treat a successful bid as successful billing.
In an authorized test environment, verify actual rendering, clicks, events, and notification deduplication, then record a separate acceptance result.
Increase traffic gradually as agreed, observing real errors, timeouts, no-bids, and creative outcomes. Public examples do not establish traffic volume or capacity.
Prepare rate reduction, pause, credential rotation, and incident steps. Confirm the live configuration works rather than relying solely on a successful configuration save.

This checklist describes work to execute, not completed formal partner acceptance, production load tests, impression billing, or settlement validation. This is a static documentation website, with no online application submission or credential-issuance function. Coordinate through existing partner channels.

References: SSP integration · DSP integration · Responses.

Protocol and implementation checked: 2026-09-21.