Let the signals shape the decision.
Turn consent and privacy signals into one per-request decision. Keep user targeting, measurement and precise geography aligned with that decision.
Coming soon. Request early access.
Example inputs and operator policy determine these permissions.
Decode once. Apply the resulting permissions.
Read the signals.
Decode TCF, applicable GPP sections and US Privacy, together with request flags such as COPPA, DNT and limited ad tracking.
Resolve the permissions.
Combine the signals with operator policy. Restrictive or unreadable inputs can move the decision to contextual processing or no-bid.
Carry the decision forward.
Downstream checks read permissions for targeting, caps, precise geography and measurement instead of interpreting raw strings again.
Make contextual buying a deliberate path.
Separate eligibility from identity.
Contextual processing can retain inventory-based matching while disabling user-level targeting, capping and measurement.
Handle conflicting signals conservatively.
The decision engine combines restrictions rather than allowing one permissive signal to cancel another restriction.
Expose the reason.
Decision reasons make it possible to inspect which signal or policy changed the request's permissions.
What changes in contextual mode?
Contextual mode retains inventory-based matching while disabling user-level targeting, frequency capping, precise geography and user-level measurement. Operator policy determines whether restricted signals permit a contextual bid or require a no-bid.
Switch to a modern,
affordable DSP.
Buy programmatically or go direct, with agentic workflows and validation included.