Troubleshooting
Diagnose the API path in this order: key class, activation, client_id, decision response, brand-safety or consent gating, then beacon delivery. That order usually exposes the real fault faster than debugging renderer details first.
Why am I not seeing ads?
Check for no-fill first. Then validate whether activation, allowed origins, blocked categories, or missing consent are gating the sponsor path intentionally.
Why is the browser path failing?
Confirm that you are using a publishable key, the active origin is allowed, and activation succeeded before calling protected runtime routes.
Why is the backend path failing?
Check the secret key, the client_id, and whether your backend is calling the canonical /v1 surface rather than older compatibility routes.
Why is billing missing?
Validate the beacon path. Rendering alone is not enough for billable completion. The missing evidence is usually in visibility or clip-completion events.
Need rollout review?
Start in the dashboard, choose Script Tag or Server API, and use contact only when you need rollout review, enterprise coordination, or non-standard integration help. Billing beacon rules live in the API concepts guide.