Start with your role
G24ad connects an SSP impression opportunity to DSP bids through admission, routing, floors, creative blocking, and a net-price auction. The SSP sends the request and receives the winning bid; DSPs receive routed requests and return bids. Exchange connection details and credentials through an agreed secure channel. This website does not collect or issue production credentials.
- SSP: Request integration → HMAC authentication → Launch checklist.
- DSP: DSP integration → Field reference → Responses and troubleshooting.
- Local verification: Examples and downloads.
Supported scope
| Area | Current boundary |
|---|---|
| Protocol | An explicit subset of OpenRTB 2.5 / 2.6-compatible JSON objects, not a full implementation |
| Impression | Exactly one imp with exactly one Banner, Video, or Native object |
| Source | Exactly one of app or site |
| Auction | Explicit at: 1, first price only; omitting at is rejected |
| Currency | USD only, without conversion; omitted request cur means USD, otherwise exactly ["USD"] |
| Unsupported | Multiple impressions, PMP / Deals, audio, ad PODs, quantity multipliers, and constraints listed in the field reference |
| Body limits | 256 KiB SSP request; 512 KiB DSP response and final SSP winning response |
| Notifications | ADX does not call nurl / burl / lurl; the SSP executes notifications against actual events |
A media object does not mean ADX has fully validated VAST, HTML, or Native creatives. Some media, secure, and privacy fields are passed through, leaving their requirements to downstream participants. Consult the classifications in the field reference.
Agree before connecting
An SSP needs its SSP ID, endpoint, protocol, audience, key ID, credential, and rotation arrangement. A DSP needs its HTTPS endpoint, OpenRTB version, explicit authentication mode, response budget, media formats, and sources. An accepted request does not guarantee an eligible route or bid. A normal no-bid response is 204.
Public examples demonstrate structure and local calculations only. This documentation is not evidence of production capacity, a latency SLA, traffic volume, or completed partner acceptance. It does not imply an impression/click service, billing ledger, or settlement service. Actual network integration, rendering, notifications, and business acceptance require separate validation.
Source specifications
Consult IAB Tech Lab OpenRTB and Native Ads for standard terminology and objects. A feature appearing in the standard does not establish G24ad support. Use the limitations in this documentation to determine the current integration scope.
Protocol and implementation checked: 2026-09-21.