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.

index.html

<script
  src="https://wavebird.ai/wavebird.js"
  data-client-id="wbproj_demo_8jK42"
  data-publishable-key="pk_test_wavebird_demo_publishable"
  data-job-type="chat">
</script>

<div
  data-wavebird-slot
  data-wavebird-formats="banner,native"
  data-wavebird-position="between">
</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.

Server-side integration

Hybrid integration

Code

Install wavebird.js

Browser-first install with publishable-key activation.

index.html

<script
  src="https://wavebird.ai/wavebird.js"
  data-client-id="wbproj_demo_8jK42"
  data-publishable-key="pk_test_wavebird_demo_publishable"
  data-job-type="chat">
</script>

<div
  data-wavebird-slot
  data-wavebird-formats="banner,native"
  data-wavebird-position="between">
</div>

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.