Graceful degradation
The sponsor path is opportunistic. Your product flow stays primary. When the API cannot or should not return a sponsored placement, the correct outcome is usually no-fill, not a broken app state.
No-fill is valid
No-fill is a normal runtime result. Treat it as a valid branch and keep the rest of the UI responsive.
Consent can block delivery
Missing or insufficient consent should prevent sponsor delivery without preventing the main product response.
Renderer must stay optional
Your UI should not depend on a successful sponsored placement. The slot can disappear, collapse, or render a safe fallback shell.
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.