Consent
Consent is enforced at the API boundary. Script Tag can collect it for you, or you can post your own consent state through the public API. Either way, routing and relevance behavior must remain bounded by the stored consent.
Collection
Supported paths
Built-in Script Tag flow
Recommended browser path. The tag can collect and store consent before the next job creation attempt.
Custom CMP
Use your own CMP or publisher UI and then store the resulting consent state through the consent endpoint.
Server-side handling
Backend integrations can carry consent state explicitly when jobs are created on the server.
Behavior
What the API enforces
TCF and jurisdiction profile
TCF 2.2 and jurisdiction hints affect whether relevance, persistence, or disclosure modes are allowed for the active request.
Fail-closed behavior
If consent or config is missing for a stricter profile, the sponsor path can resolve as no-fill while the app itself continues normally.
Need rollout review?
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.