Guide
Going live checklist
Prove the integration with nonpayable credentials, then complete the Live requirements shown for your project. Passing a test does not activate paid delivery.
Verify the deployed integration
Check every selected format and timing on the saved HTTPS origin. Confirm visible creative, real consent, withdrawal, Stop, No-Fill and matching Test Logs. A successful request or model result alone is not an ad-display check.
Complete Dashboard requirements
Resolve the project's setup, verified property/origin, integration and legal requirements shown in Dashboard. Complete the required DPA and publisher payout onboarding. Obtain the separate Live delivery approval before using a Server Production Key.
Publisher payout details are for receiving earnings. Advertiser payments fund campaigns and are a different flow. Adding payout details, creating an account or installing a package does not enable Live ads.
Production dry-run
When available, use a Server Production Dry-run Key through a compatible REST integration. It selects nonbillable delivery by credential class and needs no payout setup. Do not add undocumented billing flags to the request.
The 0.1.0-beta.19 server package currently accepts sk_test_ and sk_live_, not sk_dry_. Do not replace its ENV key with sk_dry_ or bypass the key check. Use the documented REST path for dry-run.
A successful dry-run remains billable=false. If demand readiness is absent, expect 409 ssp_not_ready. Direct server beacons are not automatically billable.
Enable and observe
After Dashboard approval, securely configure the authorized Live credential. Confirm the app still uses the correct project and origins. Monitor delivery, qualified measurement and revenue separately. Never click real ads to test billing.
Share only request IDs, fixed error categories, relative timings and redacted diagnostics when investigating failures.
Need help with your integration?
Share the affected endpoint, request ID, and the behavior you expected. Leave out keys and user content.