GPP String Decoder

Ek IAB GPP consent string apne browser mein decode karein — header, gpp_sid, aur har embedded section, readable fields mein expanded. String aapke device par rehti hai.

GPP String Decoder poori tarah aapke browser mein chalta hai. Jo consent string aap paste karte hain — aur woh jo kuch bhi decode hoti hai — aapke device par rehti hai aur kabhi ek CMP, ad server, ya ArrayKit ko nahi bheji jaati.

TCF Consent String Decoder kholein

GPP String Decoder ke baare mein

GPP String Decoder ek IAB Global Privacy Platform consent string ko kisi aisi cheez mein khol deta hai jise aap sach mein padh sakein. Ek CMP, ek OpenRTB bid request ke regs.gpp field, ya ek stored cookie se encoded value paste karein, aur tool header decode karta hai — GPP version aur gpp_sid list — plus har embedded section, TCF Europe v2 se lekar US Privacy (uspv1) aur US state signals jaise usnat aur usca tak. Har section ko named fields jaise CmpId, purpose consents, sale opt-outs, aur MSPA flags mein expand kiya jaata hai. Yeh un ad-ops engineers, privacy teams, aur QA ke liye bana hai jo programmatic supply ke across consent plumbing debug karte hain. Poora decode aapke device par chalta hai — jo GPP string aap paste karte hain woh kabhi ek CMP, ad server, ya kisi endpoint ko nahi bheji jaati.

Features

GPP String Decoder kaise use karein

  1. Apne CMP, ek OpenRTB regs.gpp field, ya ek stored __gpp value se ek GPP string copy karein
  2. Use input box mein paste karein, ya ek example string load karne ke liye Sample click karein
  3. Decoded header aur har section ke fields padhein, ya JSON view par switch karein
  4. Poora decode ya ek section copy karke ek bug report ya ticket mein attach karein

Example

Input

DBABTC~1YNN

Output

header: { version: 1, gpp_sid: [6] }
uspv1:  { Version: 1, Notice: "Y", OptOutSale: "N", LspaCovered: "N" }

Ek US Privacy (uspv1) string: notice diya gaya, koi sale opt-out nahi, LSPA-covered nahi.

Common errors aur troubleshooting

Aksar pooche jaane wale sawaal

Ek IAB GPP string kya hai?
Global Privacy Platform (GPP) string ek single encoded value hai jo multiple privacy signals — TCF Europe, US Privacy, aur US state sections — ko ek header ke peeche pack karti hai. Header ki gpp_sid list batati hai ki kaunse sections andar hain.
Ek GPP string mein gpp_sid kya hai?
gpp_sid GPP header mein section ids ka array hai. Har id ek section se map karti hai — 2 TCF EU v2 hai, 6 US Privacy hai, 7 usnat hai, 8 usca hai — ek decoder ko batati hai ki header ke baad kaunse blocks aate hain.
Yeh decoder kaunse GPP sections padh sakta hai?
Yeh header plus TCF Europe v2, TCF Canada v1, US Privacy (uspv1), US national section (usnat), aur US state sections jaise usca, usva, usco aur baaki decode karta hai, har ek ko named fields mein expand karke.
Kya main yahan ek bare TCF ya legacy US Privacy string paste kar sakta hoon?
Yeh tool ek header wali poori GPP string expect karta hai. Ek standalone TCF string jo 'C' se shuru hoti hai, ya ek legacy US Privacy value, iske bajaye dedicated TCF ya US Privacy decoders mein jaani chahiye.
Kya ek GPP string decode karne se pata chalta hai ki ek vendor allowed hai?
Nahi. Decoder dikhata hai ki string kya encode karti hai — opt-outs, purpose consents, MSPA flags — lekin yeh judge nahi karta ki ek specific vendor data process kar sakta hai; woh aapki policy aur har section ke rules par depend karta hai.
Main decode karne ke liye ek GPP string kahan dhoondhoon?
Ek CMP ki stored value, ek OpenRTB bid request ke regs.gpp field, __gpp cookie ya localStorage entry, ya CMP API ke getGPPData call se return hone wali gppString mein dekhein.

Related tools

Saare ArrayKit tools