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 requesting placements that require consent.
Record consent
record-consent.shbash
1curl -X POST https://api.wavebird.ai/v1/consent \2 -H "Authorization: Bearer sk_test_wavebird_demo_secret" \3 -H "Content-Type: application/json" \4 -d '{5 "client_id": "wbproj_demo_8jK42",6 "session_id": "sess_demo_123",7 "source": "publisher",8 "purposes": {9 "ads": true,10 "measurement": true11 }12 }'Script Tag
The Script Tag can show a consent dialog when configured, persist the decision, and send consent state to the API.
Need rollout review?
Start with the Server API. Use contact only when you need rollout review, enterprise coordination, or non-standard integration help.