Privacy & Consent
Anima can pass consent signals and privacy flags into your ad stack. You configure them once, and they're baked into your wrapper configuration when you deploy a release.
This page describes the settings on Account → Setup → Privacy. The field names are accurate; the on-screen layout is being captured.
These settings let you pass the consent and privacy signals you've decided on into the auction and ad server. They don't, by themselves, make your site compliant with GDPR, CCPA, or any other regulation — that's a decision you make with your own legal/privacy guidance.
Where it lives
Account mode → Setup → Privacy. Settings are scoped to a customer or a single domain (domain-level settings override customer-level for that domain), and they take effect when you next deploy a wrapper release.
GPP consent management
Anima supports the IAB Global Privacy Platform (GPP) consent module in Prebid:
| Setting | What it does |
|---|---|
| GPP Enabled | Turns on the GPP consent-management module in the wrapper |
| GPP Timeout | How long (in milliseconds) the wrapper waits for your CMP before proceeding — default 10000 |
| GPP Timeout Action | What to do if the CMP doesn't respond in time (e.g. cancel). Leave blank to use Prebid's default |
You supply the CMP; Anima wires the GPP module to it and forwards the resulting consent string to bidders.
Google Publisher Tag (GPT) privacy flags
Four GPT privacy flags can be set on your ad requests. Each is three-state — leave it unset to not touch GPT's default, or set it explicitly to on/off:
| Flag | Effect when set |
|---|---|
| Restrict Data Processing | Sets restrictDataProcessing on GPT (e.g. for CCPA "do not sell") |
| Child-Directed Treatment | Sets childDirectedTreatment (COPPA) |
| Under Age of Consent | Sets underAgeOfConsent |
| Non-Personalized Ads | Requests non-personalized ads only |
Leaving a flag unset means Anima doesn't set it — GPT keeps its own default behavior.