Consentik Wix: show your TCF banner in your visitors' languages
Consentik Wix: show your TCF banner in your visitors' languages
Your IAB TCF banner can now appear in the language each visitor is reading your site in, instead of one language for everyone. This article explains what changed, how to set it up, and what visitors see when a language is not available.
This applies to sites with the IAB TCF banner turned on and the Multiple Language feature enabled. If you use the standard cookie banner, your multilingual setup is unchanged and nothing here affects you. If you run TCF in a single language, see Nothing changes for a single-language site at the end.
What changed
Before, the TCF banner was single-language. You picked one language in the Language template control on the IAB TCF page, and every visitor saw that language — a visitor in Paris and a visitor in Berlin read the same text. Switching the language in that control also replaced the text you had written, so you could not keep wording for two languages at once.
Now, the TCF banner, the preferences popup, all of its tabs and the vendor details follow the visitor's language, and each language keeps its own text.
Your TCF popup follows the visitor's language. It uses the same language detection you already configured for the cookie banner under Translations — URL subdirectory, subdomain, query parameter, browser or visitor location. You do not configure detection a second time for TCF.
Purpose and Feature text comes from IAB, already translated. The names and descriptions of Purposes, Features and Special Features are published by IAB Europe in each language, and Consentik uses their text as published. On the content tab these appear in a read-only block, badged as IAB's and labelled with the GVL version they came from, so you can see what visitors read without hunting for a field to edit. IAB's own policies do not allow consent platforms to reword these definitions.
Each language keeps its own text. Switching language no longer overwrites what you wrote. Edit German, save, switch to French, and your German wording is still there.
TCF text is now edited in one place. Per-language TCF text lives in an Edit language card on the IAB TCF v2.4 page.

Which languages TCF can serve
Language scopes lets you pick from 189 languages. IAB publishes TCF translations for 55 of them. All 189 remain selectable — your cookie banner, categories and data requests still work in every language you pick — but TCF only follows those 55.
To make this visible before you commit, Translations → Language scopes now marks each language:
- a globe means Consentik ships ready-made text for your cookie banner, categories, data requests and EU withdrawal in that language;
- an IAB chip means IAB publishes TCF purpose text in that language.
The marks appear in the picker and on the languages you have already selected, with a legend under the field. Pick a language without the IAB chip and Consentik tells you in a full sentence what TCF will do instead. The IAB chip and its legend line only appear while your site has TCF switched on.

How to set it up
- In the Consentik dashboard, open Translations.
- Turn on Multiple Language if it is not already on, and choose your detection method.
- Under Language scopes, select the languages your site serves and press Save. Languages only become editable after you save.
- Open IAB TCF v2.4 from the left menu.
- In the Edit language card above the tabs, pick a language. The fields and the live preview switch to it, so you can read the popup as a visitor would.
- Edit the text you own — messages, button labels, link text, tab and section titles — and save. Repeat for each language.
Your default language carries whatever you had already written. Languages you add arrive pre-translated rather than in English, so an untouched language is still readable on day one.
What visitors see when a language is missing
A visitor never sees two languages on one screen. If a language cannot be served, the whole TCF surface falls back together — never the chrome in one language around IAB's text in another.
A visitor whose language you do not serve gets your site's default language, in full.
If your site's default language has no IAB translation, TCF renders entirely in English, and Consentik shows you a banner on the IAB TCF page explaining why. English or nothing are the only options IAB's policies leave open here.
If a secondary language has no IAB translation, TCF does not serve that language at all; those visitors get your default language instead. This is deliberate — forcing English on them would replace a perfectly readable default-language popup with a worse one.
Things worth knowing
- Some settings are shared across every language. Colours, vendor selection, Google Additional Consent and the active toggle apply to your whole site. Select a language other than your default and these stay on screen but become read-only, under a banner explaining that they are shared. Switch back to your default language to change them.
- Save before switching language. With unsaved edits, the language selector is disabled and a warning tells you to save or discard first. Consentik will not discard your work for you.
- Every field must be filled in. If you clear a field and save, the save is refused, the empty fields are flagged, and a line tells you how many are empty — because a visitor would see English in those spots, not your default language. Consentik deliberately does not fill them from another language, which would ship text in the wrong language without telling anyone.
- Nothing changes for a single-language site. If you have not enabled Multiple Language, the IAB TCF page looks exactly as it did, with the Language template control in its usual place and no language selector. Turn Multiple Language off again and that control comes back unchanged.
- If your plan stops including Multiple Language, your TCF banner immediately serves your base content again, and your translations are kept for if you upgrade later.
- Check your live site in a private or incognito window — a normal window may still show a cached version of the banner.
Why it matters
Consent has to be informed to count, and a visitor cannot give informed consent to a notice they cannot read. Serving the TCF popup in the visitor's language — with IAB's own wording for the Purposes, in IAB's own translation — removes the most obvious gap in a multilingual store's consent flow.
Whether your site as a whole meets your legal obligations depends on how you collect and use data. If you are unsure, ask your legal adviser.
Need help?
Contact Consentik support, or read IAB Europe's documentation on the Transparency & Consent Framework.
Updated on: 12/11/2026
Thank you!