Skip to main content
@cookiechimp/translations ships banner and preferences messages for 33 locales. Each locale is its own entry, so you only bundle what you import.
In Next.js, pass languages and a translations resolver to CookieChimpProvider. The server negotiates the language from Accept-Language:
Locales: en, de, fr, es, it, nl, pt, pt-BR, pl, sv, da, fi, no, cs, sk, hu, ro, bg, el, hr, sl, et, lv, lt, ga, mt, tr, ja, zh, ko, ar, he and uk. ar and he are right to left (rtlLocales). localeMeta records editorial review status for all 33 locales. translationReview from @cookiechimp/translations/meta records the review method and date.

Platform JSON content

The platform UI uses the banner and nested category/vendor translations from your existing JSON. Pass locale explicitly or use configured browser/document hints. Region suffixes such as fr-CA select configured base language fr. The selected banner language and RTL settings apply to the UI. Translate the consent-ID label through CookiePreferences consentIdLabel; it defaults to “Your consent ID”.

TCF labels

The IAB TCF vendor list has its own labels in opt-in entries, so the banner bundles above do not grow:
All 33 TCF label sets have completed editorial review (tcfReviewedLocales from @cookiechimp/translations/tcf). Numeric duration labels preserve the {days} placeholder and use wording that works for singular and plural values. Purpose, feature and vendor names come from the GVL; supply it in the same language as the interface.