Developer FAQ
The questions below assume the API-first model. Use the SDK only as a secondary option when you already know why the direct Script Tag or Server API path is not enough.
Do I need the SDK to integrate wavebird?
No. The API is now the primary surface. Most teams should start with Script Tag or direct Server API calls. The SDK is optional.
What is the recommended browser path?
Script Tag. It gives you the browser-safe activation path, consent handling, rendering, and beacon wiring on top of the same public API contract.
What is the canonical backend path?
The canonical backend path is the public /v1 API with a secret key. That is the primary server reference surface.
What must I verify before moving to live keys?
Validate activation or server auth, confirm decision shapes, test no-fill branches, and make sure the beacon path is complete for the formats you ship.
Need help diagnosing no-fill?
Start with the API troubleshooting page before you debug renderer details.
Open troubleshooting →Need the SDK on purpose?
Use the advanced SDK page and the SDK reference once the API model itself is already clear.
Open advanced SDK →Open full SDK docs →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.