Translations

@cookiechimp/translations ships banner and preferences messages for 33 locales. Each locale is its own entry, so you only bundle what you import.

import { ConsentProvider } from "@cookiechimp/react";
import de from "@cookiechimp/translations/de";

<ConsentProvider config={config} translations={de} language="de">
  ...
</ConsentProvider>;

In Next.js, pass languages and a translations resolver to CookieChimpProvider. The server negotiates the language from Accept-Language:

import { CookieChimpProvider } from "@cookiechimp/nextjs/server";
import de from "@cookiechimp/translations/de";
import en from "@cookiechimp/translations/en";

const messages = { en, de };

<CookieChimpProvider
  config={config}
  languages={{ available: ["en", "de"], fallback: "en" }}
  translations={(locale) => messages[locale as keyof typeof messages]}
>
  {children}
</CookieChimpProvider>;

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.

TCF labels

The IAB TCF vendor list has its own labels in opt-in entries, so the banner bundles above do not grow:

import { TcfVendorList } from "@cookiechimp/react/tcf";
import de from "@cookiechimp/translations/tcf/de";

<TcfVendorList controller={tcf} labels={de} />;

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.

Get started

SDK reference

TCF labels

​TCF labels

TCF labels