Guide
Hybrid integration
Quick answer
A hybrid integration keeps the secret-key placement call on the backend while the frontend controls when to display the returned placement.
Load render.js in the browser for the hosted frame and never pass the server secret key to that browser.
Hybrid integrations let the backend own secret-key placement requests while the browser owns display timing through render.js.
Backend creates the placement
Call /v1/placements server-side and return the canonical decision response to the frontend.
Frontend renders
The frontend loads /v1/render.js, calls wavebird.withTurn(), and renders a hosted iframe from placement.render.
Security boundary
Do not pass secret keys to the browser. Use short-lived session state if the browser needs to call browser-safe endpoints.
Need rollout review?
Start with the Server API. Use contact only when you need rollout review, enterprise coordination, or non-standard integration help.