Guide

Client-side integration

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.

Install wavebird.js

index.htmlhtml
1<script2  src="https://wavebird.ai/wavebird.js"3  data-client-id="wbproj_demo_8jK42"4  data-publishable-key="pk_test_wavebird_demo_publishable"5  data-job-type="chat">6</script>7 8<div9  data-wavebird-slot10  data-wavebird-formats="banner,native"11  data-wavebird-position="between">12</div>

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.