Script Tag
Script Tag troubleshooting
Most Script Tag issues are caused by origin mismatches, missing slots, or blocked network calls.
Origin mismatch
If activation returns `forbidden` with an origin-mismatch message, add the exact origin to the publishable key in the dashboard. Include scheme and port for local development.
No slot rendered
Confirm the page has a data-wavebird-slot element before the script initializes, or call the public API after dynamically inserting slots.
Missing beacons
Check that render and visibility events are not blocked by CSP, ad blockers, or page lifecycle interruptions.
Need rollout review?
Contact the team
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.