Guide

Client-side integration

Connect Script Tag rendering to your browser page and verify the result.

Make the slot available

Add wavebird.js and one or more data-wavebird-slot elements. The slot must exist when the script discovers it. Keep its dimensions stable while an ad loads.

Activate the correct project

Use a publishable key and configure the exact origin, including the local port. Server secrets must never appear in browser markup.

Installation and origins →Slot markup →

Check the browser lifecycle

Enable ?wavebird-debug=1 during integration. Confirm activation, required consent, rendering, and beacons. Test a missing or blocked ad response and check that the rest of the page still works.

Events and diagnostics →Browser troubleshooting →

Need help with your integration?

Share the affected endpoint, request ID, and the behavior you expected. Leave out keys and user content.

Contact the team