Guide
Consent in consumer AI apps
Quick answer
Collect the consent required for a sponsored interaction before requesting a placement that relies on it.
Synchronize publisher or CMP session state through /v1/consent when needed, or include the documented request-level flags on the placement call.
Consent should be collected before sponsorship decisions that require ads or measurement purposes.
Consent timing
Collect consent before requesting placements for sessions that may render sponsored assets.
Store consent
Use /v1/consent when your app or CMP owns session/user-level consent state. Use request-level placement consent inside /v1/placements for per-request privacy and targeting signals; no separate sync is required before placement when those flags are present.
Fallback behavior
If consent is missing, use a no-fill or non-personalized path rather than blocking the user flow.
Need rollout review?
Start with the Server API. Use contact only when you need rollout review, enterprise coordination, or non-standard integration help.