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
If your app or CMP owns session-level consent, synchronize it through /v1/consent. If consent is carried on the placement request, a separate sync is not required for that request.
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.