Guide
Consent in consumer AI apps
Place consent handling in the AI interaction without making the AI task depend on an ad.
Before a sponsored interaction
Collect the permission required for rendering and measurement before requesting the corresponding placement. Keep the AI response independent of whether the user accepts or declines.
When the user decides
Use the selected project's complete backend and frontend lifecycle handlers. Include client_id, the same session_id, the actual lifecycle_state, a positive increasing revision, the profile's genuine decision source and canonical purposes. Verify the returned authoritative snapshot before rendering; source labels and inline flags cannot manufacture a user's decision.
Project-scoped ENV, BACKEND and FRONTEND guide →Consent endpoint reference →
| Project profile | Decision source and responsibility |
|---|---|
| Own CMP (own_cmp) | Your application owns the actual per-user, per-conversation choice. Synchronize it as publisher_custom through /v1/consent; placement privacy metadata uses wrapper_cmp. Those labels describe the source, not a grant of permission. |
| wavebird dialog (wavebird_consent) | Use the genuine wavebird dialog and synchronize its actual choice as wavebird_dialog. The project requires a current stored record for the authenticated tenant, project and session before placement; inline flags cannot replace it. |
One user's conversation lifecycle
Bind consent, placement and withdrawal to the same anonymous session for one user conversation. Create fresh state when the user or conversation changes; never reuse a shared demo session or replay a cached grant.
Grant only after an explicit current choice. Denial, withdrawal, expiry or an unavailable consent state keeps the slot hidden, cancels pending sponsor work and prevents late rendering and ad beacons. Purpose flags do not grant lifecycle permission.
Preserve observed Sec-GPC across the browser and backend. A positive signal blocks advertising admission; do not strip the signal, protocol strings or denied permission to make a request succeed.
Keep the primary chat stream available without waiting for consent or an ad. Request sponsorship only at the saved Before, During or After phase. Let the package apply format-specific cleanup when generation ends. After work waits for completion and output presentation. Bound each phase's lifetime and cancel it when the conversation changes or its permission is lost.
When permission changes
A missing, expired, or revoked lifecycle decision prevents rendering and beacons. Disabling only semantic targeting is different: permitted non-personalized product context may remain usable under the active rules. Never use a fallback to bypass required permission.
Need help with your integration?
Share the affected endpoint, request ID, and the behavior you expected. Leave out keys and user content.