TCF Consent String Encoder
CMP settings, purpose consents, special features aur vendor ids se ek IAB TCF v2.2 Transparency & Consent (TC) string banayein — aapke browser mein encoded.
TCF Consent String Encoder poori tarah aapke browser mein chalta hai. Aapki CMP settings, purpose selections aur vendor ids aapke device par encode hote hain, koi Global Vendor List fetch nahi hoti, aur kuch bhi ArrayKit ko upload nahi hota.
TCF Consent Decoder kholein
TCF Consent Encoder ke baare mein
TCF Consent String Encoder ek form se ek IAB TCF v2.2 Transparency & Consent (TC) string banata hai: apni CMP ID, CMP version, consent screen, consent language, vendor list version aur TCF policy version set karein, phir purpose consents (1-11), purpose legitimate interests, special feature opt-ins aur vendor consent ids ki ek list toggle karein. Yeh ek valid TCModel assemble karta hai aur base64url TC string produce karta hai jise aap ek CMP fixture, ek Prebid config, ek ad request, ya ek QA test mein paste kar sakein. Yeh tab kaam aata hai jab ad-ops engineers aur CMP developers ko ek consent scenario reproduce karne ya debug karne ke liye ek deterministic string chahiye ki ek demand partner kyun drop ho raha hai. Har field aapke device par encode hota hai — koi CMP API call nahi hota aur koi global vendor list network se fetch nahi hoti, isliye test consent data kabhi aapke browser se bahar nahi jaata.
Features
- Simple fields se CMP ID, CMP version, consent screen aur consent language set karein
- vendor list version, TCF policy version aur service-specific vs global scope chunein
- Consent aur legitimate interest ke liye saare 11 registered purposes toggle karein
- Do special features (precise geolocation, device scanning) mein opt in karein
- Vendor consent ids ki ek comma-separated list ko vendor section mein encode karein
- Ek base64url TC string output karta hai jise aap ek click mein copy kar sakein
- Deterministic encoding taaki same selections hamesha same string dein
- Poori tarah aapke browser mein chalta hai, koi vendor list network se fetch nahi hoti
TCF Consent Encoder kaise use karein
- Apni CMP ID, CMP version, consent screen aur two-letter consent language enter karein
- vendor list version, TCF policy version aur storage scope toggle set karein
- Woh purposes, legitimate interests aur special features check karein jinmein user ne opt in kiya
- Vendor consent ids ko ek comma-separated list ke roop mein type karein
- Encoded TC string copy karke apne CMP, ad request ya test fixture mein daalein
Example
Input
cmpId: 300, cmpVersion: 1, lang: EN
purposeConsents: 1,2,3,4,7
vendorConsents: 1,8,755
Output
COzTVhaOzTVhaGvAAAENAiCIAP_AAH_AAAAAAAAA... (base64url TC string)
Selected purposes aur vendor ids ek TCF v2.2 core string mein pack ho jaate hain.
Common errors aur troubleshooting
- Jo vendor id aapne add ki woh string decode hone par missing hai. — TCF encoder vendor consents ko ek vendor list ke against validate karta hai. Yeh tool har id ko declare karta hai jo aap enter karte hain taaki woh survive kare — output ko yahan ya TCF Consent Decoder mein decode karke confirm karein ki vendor bit set hai.
- Decoded consent language woh nahi hai jo aapne type ki. — TCF v2.2 consent language ko two-letter uppercase (EN, FR, DE) par force karta hai. Bilkul do letters enter karein; tool encode karne se pehle unhe uppercase karta hai.
- Ek downstream CMP string ko ek cmpId error ke saath reject karta hai. — CMP IDs 0 aur 1 reserved hain aur kai decoders unhe reject karte hain. Real IAB-assigned CMP ID use karein (1 se bada ek integer).
- Decoded string mein vendor list version aapke input se alag hai. — Encoded vendor list version aur TCF policy version un values se aate hain jo aap metadata fields mein enter karte hain — unhe us GVL se match karne ke liye set karein jo aapka CMP run kar raha hai.
Aksar pooche jaane wale sawaal
- Ek TCF consent string encoder kya hai?
- Yeh ek tool hai jo CMP settings aur user consent choices — purposes, legitimate interests, special features aur vendor ids — ko ek IAB TCF v2.2 Transparency & Consent (TC) string mein badalta hai, woh base64url value jo CMPs vendors aur ad requests ko pass karte hain.
- Yeh encoder kaunsa TCF version produce karta hai?
- Yeh TCF v2.2 core strings banata hai. Aap TCF policy version aur vendor list version fields control karte hain, aur output ek standard base64url TC string hai jise TCF-aware CMPs aur decoders padh sakte hain.
- Main string mein vendor consents kaise add karoon?
- IAB vendor ids ko vendor consent field mein ek comma- ya space-separated list ke roop mein type karein (jaise 1, 8, 755). Har id TC string ke vendor-consent section mein encode ho jaati hai.
- consent language do letters ki kyun honi chahiye?
- TCF spec consent language ko ek two-character ISO-639-1 code ke roop mein store karta hai. Encoder aapke input ko uppercase aur validate karta hai, isliye poore language names ke bajaye EN, FR ya DE jaise codes enter karein.
- Kya encoding Global Vendor List ko ek server se fetch karti hai?
- Nahi. Poori tarah aapke browser mein rehne ke liye, tool GVL download karne ke bajaye aapke enter kiye ids se ek minimal in-memory vendor list banata hai. Aapki CMP settings aur vendor ids kabhi kahin nahi bheje jaate.
- Kya main yahan banayi ek string decode kar sakta hoon?
- Haan. Encoded output ko TCF Consent Decoder mein paste karke CMP fields, purposes aur vendors inspect karein aur confirm karein ki string expected roop se round-trip karti hai.
Related tools
Saare ArrayKit tools