Guide
Going live checklist
Quick answer
Before live traffic, verify credential storage, allowed origins, configuration defaults, placement rendering, beacons, logs, and fallback behavior together.
Use the non-billable production dry-run credential class for pre-live verification; it is not a substitute for a production-live approval.
Before switching to live traffic, verify keys, origins, config defaults, decisions, beacons, logs, and fallback behavior.
Keys and origins
Create live keys, store secrets securely, and configure production origins for publishable keys.
End-to-end flow
Run placement creation, hosted rendering, consent, and beacon tests against live-shaped configuration.
Production dry-run
Use production-dry-run before any live billing approval. Create a Server Production Dry-run Key in Dashboard API Keys or request an operator-issued sk_dry_... server key, then use it as WAVEBIRD_SECRET_KEY for the existing server integration.
Dry-run proof can show proof_eligible=true and proof_would_be_eligible=true while billable=false, billing_suppressed=true, dry_run_billable_suppressed=true, production_live_approved=false, and non_billable_reason=PRODUCTION_DRY_RUN_NON_BILLABLE.
Production dry-run is non-billable, requires no payout setup, and does not use a production-live-approved mode. Direct server beacons remain DIRECT_BEACON_NOT_BILLABLE unless a separate trusted measurement policy is approved. If no active SSP demand is available, placement creation returns 409 ssp_not_ready with mode=production-dry-run, production_dry_run=true, production_live_approved=false, and billable=false.
Support readiness
Capture request IDs for failed requests and confirm dashboard logs show enough detail for first-line diagnosis.
Need rollout review?
Start with the Server API. Use contact only when you need rollout review, enterprise coordination, or non-standard integration help.