Documentation that matches behavior.
The documentation is organized so an engineer can go from install to first ad request without a call, and so that what the docs say is what the code does. Structure and access are described here.
Install to first ad request · one sitting
From quickstart to changelog, one path through.
Quickstarts
One per platform: install to first ad request in a single sitting, with copy-ready snippets and the test-mode validation steps at the end.
SDK reference
Format and mediation APIs per platform and version, including minimum OS versions, permission reasons and the consent flags.
API reference
Reporting and server-to-server endpoints with authentication, rate limits and error codes, plus example requests that run against the sandbox.
CTV integration
SSAI setup per TV platform: manifest handling, VMAP pod plans, beacon forwarding and store listing checks.
Mediation setup
Network configuration, waterfall policy, optimization settings and the migration path from direct SDK stacks.
Troubleshooting
Grouped by symptom, not by component: no fill, integration errors, reporting gaps. Each symptom page ends with when to escalate.
Changelog
Release notes for SDK versions and platform changes, with deprecation notices and their windows stated at the top.
What is public, what comes with the account.
The guides on this site and the platform pages are public. Full technical documentation, SDK reference binaries and API credentials are provisioned with your account during onboarding, so version numbers and endpoints in the reference always match what your integration actually uses. If you are evaluating before an account exists, the integration contact sends the evaluation pack.
From docs to the support queue.
The troubleshooting section is the first stop: it covers the common symptoms with their checks. When a symptom survives the documented checks, the support queue takes over with the integration ID and the debug log attached. Standard publishers use the support channel from onboarding; managed accounts go through their named contact. Login and access problems belong with that same support channel, the address ships with your onboarding, not with the technical queue.
Docs that match what ships.
Evaluating or already integrating: the docs team and the integration engineers are the same people, and the fastest path in is a short message.
Quickstarts · SDK reference · API reference · changelog