Ad-Server Consent Signals
One call returns every signal your ad stack needs — gdpr_consent, GPP, Google Additional Consent, npa, ltd and more — ready to inject into GAM, IMA, OpenRTB and Prebid.
Every consent signal your ad stack needs — from one call.
Monetised sites and apps don't just need consent — they need consent in the exact shape ad servers expect. Cookie Panda turns the user's live consent state into a single ready-to-inject object: the IAB TCF v2.3 TC string (gdpr_consent), the GPP string and section IDs, the Google Additional Consent string (addtl_consent), plus the derived ad-request flags publishers always end up hand-computing — npa (non-personalised ads), ltd (limited ads), rdp (restrict data processing) and the legacy us_privacy string.
On the web it's a one-liner — window.CookiePanda.getAdParams() — that you drop straight into a Google Ad Manager tag, an IMA/VAST request, a Prebid config or an OpenRTB call. Before a decision it returns privacy-safe defaults, so an early ad call is never accidentally personalised. On mobile and CTV the same signals are written to the standard IAB in-app keys (IABTCF_, IABGPP_) and the server-side CTV lookup returns GPP for your OpenRTB regs object.
The result: your ad ops team stops writing brittle glue code to translate consent into macros, and every impression carries a correct, auditable consent signal — which is exactly what Google and your SSPs require to keep serving programmatic demand in regulated markets.
What's included
getAdParams() → ready-to-inject values
TC string, GPP + Google AC string
npa / ltd / rdp + us_privacy derived for you
Web, mobile & CTV (OpenRTB regs.gpp)
Ad-Server Consent Signals in four steps
- 1
Collect consent as normal
The banner (or your known-age auto-flag) records the user's choice and builds the TC / GPP / AC strings.
- 2
Call getAdParams()
Get back gdpr, gdpr_consent, addtl_consent, gpp, gpp_sid, us_privacy, npa, ltd and rdp in one object.
- 3
Inject into your ad request
Pass the values straight into GAM/IMA URL macros, Prebid's consent module, or your OpenRTB bid request.
- 4
Stay current automatically
Re-read after any consent change — values reflect the latest state, including GPC and opt-outs.
Common questions
Which ad platforms does this work with?
Anything that reads IAB signals — Google Ad Manager / AdSense, IMA & VAST for video/CTV, Prebid, and OpenRTB SSPs. getAdParams() also derives Google's npa/ltd/rdp flags so you don't have to.
What happens before the user consents?
getAdParams() returns privacy-safe defaults for the user's region (e.g. npa=1, ltd=1 in the EU), so any ad call made before a decision stays non-personalised.
Does it cover mobile and connected TV?
Yes. Native SDKs write the standard IABTCF_/IABGPP_ in-app keys that ad SDKs read, and the CTV server lookup returns the GPP string for your OpenRTB regs.gpp field.
More features
Consent Banner Designer — Design a fully on-brand consent experience with four layouts, live preview, and per-locale copy — no code required.
Automated Cookie Scanner — A headless Chromium crawler discovers every cookie, tracker and third-party vendor on your site and keeps your policy in sync.
Prior Cookie Blocking — Stop trackers before consent. Cookie Panda rewrites and gates tag-loading scripts until the user makes a choice.
Get compliant today. Stay compliant for good.
Join the teams using Cookie Panda to turn privacy compliance from a liability into a signal of trust. Free to start — no credit card required.