Guide
Hybrid integration
Connect a backend placement response to the browser UI without exposing server credentials.
Backend creates the placement
Call /v1/placements with the server key. Return the placement, decision, and authoritative_consent fields needed by the hosted renderer. Keep secrets on the server.
Frontend decides when to display it
Load /v1/render.js. When a filled response is ready and the slot is still relevant, call wavebird.renderPlacement(). Clear the slot for no-fill and retain the returned cleanup function for replacement or removal.
Keep activation separate
A browser calling browser-authorized endpoints needs the documented activation token. Receiving a placement from your backend does not require sharing its secret key or creating a new browser authentication scheme.
Need help with your integration?
Share the affected endpoint, request ID, and the behavior you expected. Leave out keys and user content.