Guide
Client-side integration
Quick answer
Use the client-side guide when a browser slot should activate, render, collect configured consent, and send beacons with minimal app code.
Only a publishable key belongs in the markup, and every tested origin must be configured before activation.
Use the Script Tag when the browser should own activation, rendering, consent, and beacon wiring.
Add markup
Add wavebird.js and one or more data-wavebird-slot elements.
Use publishable keys
Only publishable keys belong in the browser. Configure all allowed origins before testing.
Verify with debug mode
Use ?wavebird-debug=1 and confirm activation, consent, render, and beacon messages appear without console errors.
Need rollout review?
Start with the Server API. Use contact only when you need rollout review, enterprise coordination, or non-standard integration help.