Core concepts

Consent model

Consent can be collected by the publisher, a CMP, or the Script Tag dialog, then stored through /v1/consent.

Consent sources

Use the source field to distinguish publisher, CMP, and wavebird-managed consent records. Store only the consent state needed for advertising and measurement.

API sync

Custom consent flows should call /v1/consent before creating jobs that require consent.

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
    }
  }'

Script Tag

The Script Tag can show a consent dialog when configured, persist the decision, and send consent state to the API.

Proof chain

Ad formats

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.