TCF Consent String Decoder
Ek IAB TCF v2.2 consent string ko apne browser mein decode karein taaki CMP metadata, purpose aur vendor grids, aur publisher restrictions dekh sakein.
TCF Consent String Decoder poori tarah aapke browser mein chalta hai. Jo consent string aap paste karte hain woh aapke device par decode hoti hai, kabhi ArrayKit ko upload nahi hoti, aur koi Global Vendor List ya remote endpoint contact nahi kiya jaata.
TCF Consent String Encoder kholein
TCF Consent Decoder ke baare mein
TCF Consent String Decoder ek IAB Transparency & Consent (TC) string ko khol deta hai taaki ad-ops aur privacy engineers dekh sakein ki ek CMP ne asal mein kya record kiya. base64url string paste karein aur yeh core segment locally decode karta hai: CMP id aur version, jis screen aur language par choice capture hui, created aur last-updated timestamps, Global Vendor List version, aur TCF policy version. Phir yeh har bitfield ko readable id lists mein expand karta hai — purpose consents, purpose legitimate interests, special feature opt-ins, vendor consents, vendor legitimate interests, aur koi bhi publisher restrictions. Ise ek failing consent handshake debug karne, ek tag ne asal mein kya store kiya audit karne, ya ek value confirm karne ke liye use karein isse pehle ki woh aapke ad server tak pahunche. String aapke browser mein decode hoti hai aur kabhi aapke device se bahar nahi jaati.
Features
- IAB TCF v2.2 core-segment metadata decode karta hai: CMP id, version, screen, aur consent language
- purpose consents aur purpose legitimate interests ko readable id lists mein expand karta hai
- special feature opt-ins ko vendor consent aur legitimate-interest grids ke saath dikhata hai
- publisher purpose restrictions ko unke restriction type aur affected vendors ke saath surface karta hai
- created aur last-updated timestamps plus Global Vendor List version display karta hai
- service-specific vs global scope, non-standard texts, aur OOB support flag karta hai
- Kisi bhi id list ko ek comma-separated string ke roop mein ek bug report ya ticket ke liye copy karein
- Poori tarah aapke browser mein chalta hai — consent string kabhi upload nahi hoti
TCF Consent Decoder kaise use karein
- TC string ko ek CMP cookie, ek __tcfapi callback, ya ek OpenRTB user.ext.consent field se copy karein
- Use decoder mein paste karein, ya ek example TC string load karne ke liye Sample click karein
- CMP metadata padhein, phir purpose, special-feature, aur vendor grids scan karein
- Apni team ke saath exact consent state share karne ke liye koi bhi id list copy karein
Example
Input
COvFyGBOvFyGBAbAAAENAPCAAOAAAAAAAAAAAEEUACCKAAA
Output
CMP 27 · policy v2 · language EN · GVL 15
purposeConsents: 1, 2, 3
vendorConsents: 2, 6, 8
Ek core-only TC string apne CMP metadata aur consent grids mein decode kiya gaya.
Common errors aur troubleshooting
- Decoder report karta hai ki string ek valid TC string nahi hai. — Poori base64url TC string bina surrounding quotes ya line breaks ke paste karein. Ek truncated core segment ya ek URL-encoded copy (= ki jagah %3D) decode hone mein fail ho jaayegi.
- purpose ya vendor lists expected se chhoti lagti hain. — Ek TC string sirf woh ids store karti hai jo CMP ne explicitly set kiye. Jo ids absent hain unhe consent nahi diya gaya. Confirm karein ki aapne poori string paste ki, sirf pehle period se pehle ka segment nahi.
- Timestamps kai hours off lagte hain. — TCF timestamps day-level UTC precision par store hote hain. Decoder unhe UTC mein dikhata hai, isliye ek local log se compare karne se pehle apne local time zone mein convert karein.
- Aapne vendor names expect kiye lekin sirf numbers dikhte hain. — Vendor aur purpose names IAB Global Vendor List se aate hain, jise yeh tool fetch nahi karta. Numeric id ko metadata mein dikhaye gaye Global Vendor List version ke against match karein.
Aksar pooche jaane wale sawaal
- Ek IAB TCF consent string kya hai?
- Ek TCF (Transparency & Consent Framework) string ek compact base64url record hai jo ek Consent Management Platform ek user ke ad-tech consent choices store karne ke liye likhta hai — kaunse purposes, special features, aur vendors unhone allow kiye. Ad tags aur OpenRTB requests ise carry karte hain taaki downstream vendors jaanein ki woh kya kar sakte hain.
- Decoder vendor aur purpose numbers names ke bajaye kyun dikhata hai?
- Vendor aur purpose names IAB Global Vendor List mein rehte hain, jo ek network par load hoti hai. Yeh tool sirf woh string decode karta hai jo aap paste karte hain aur koi network calls nahi karta, isliye yeh numeric ids exactly as encoded dikhata hai. Vendor name paane ke liye ek id ko current Global Vendor List mein look up karein.
- Main paste karne ke liye TC string kahan dhoondhoon?
- Yeh euconsent-v2 cookie mein store hoti hai, CMP ke __tcfapi('getTCData', ...) call se return hoti hai, aur ek OpenRTB bid request mein user.ext.consent ke roop mein pass hoti hai. In mein se koi bhi base64url value copy karke decoder mein paste karein.
- service-specific aur global scope mein kya farak hai?
- isServiceSpecific bit record karta hai ki consent ek site ya service (true) ke liye store hua ya shared global consensu.org scope (false) mein. Decoder is bit ko surface karta hai taaki aap bata sakein ki signal properties ke across kitna portable hai.
- Kya ek TC string decode karne se woh change ya re-sign hoti hai?
- Nahi. Decoding read-only hai — yeh existing bits ko re-encode, re-sign, ya alter kiye bina interpret karta hai. Aapki original TC string unchanged rehti hai aur sirf aapke browser mein locally read hoti hai.
- Kya yeh publisher restrictions aur extra segments padh sakta hai?
- Haan. Yeh core segment ko poori tarah decode karta hai aur publisher purpose restrictions ko unke restriction type aur affected vendors ke saath list karta hai. Jo fields ek string include nahi karti — jaise absent optional segments — woh simply empty dikhte hain.
Related tools
Saare ArrayKit tools