Guide

Consent in GenAI apps

Consent should be collected before sponsorship decisions that require ads or measurement purposes.

Consent timing

Collect consent before creating jobs for sessions that may render sponsored assets.

Store consent

Use /v1/consent when your app or CMP owns the consent UI.

record-consent.sh

curl -X POST https://api.wavebird.ai/v1/consent \
  -H "Authorization: Bearer sk_test_wavebird_demo_secret" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "wbproj_demo_8jK42",
    "session_id": "sess_demo_123",
    "source": "publisher",
    "purposes": {
      "ads": true,
      "measurement": true
    }
  }'

Fallback behavior

If consent is missing, use a no-fill or non-personalized path rather than blocking the user flow.

Hybrid integration

Configuration

Code

Record consent

Sync publisher consent into the public API.

record-consent.sh

curl -X POST https://api.wavebird.ai/v1/consent \
  -H "Authorization: Bearer sk_test_wavebird_demo_secret" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "wbproj_demo_8jK42",
    "session_id": "sess_demo_123",
    "source": "publisher",
    "purposes": {
      "ads": true,
      "measurement": true
    }
  }'

Need rollout review?

Contact the team

Start in the dashboard, choose Script Tag or Server API, and use contact only when you need rollout review, enterprise coordination, or non-standard integration help. Billing beacon rules live in the API concepts guide.