Banner
HOMEPAGE | HELP GUIDES | BANNER | CONTENT AND LANGUAGES

Content and languages

Banner texts, button labels and languages.

Languages

In Banner Builder → General → Language Settings:

  • Supported Languages: the languages your banner is available in. English is always included.
  • Default Language (Fallback): used when the visitor's language is not in your list.

Okito picks the language from the page (<html lang>, a language in the URL path such as /de/) and the visitor's browser. More than one language needs the Beginner plan or higher.

On a website whose country is Türkiye, a visitor whose browser is set to Turkish gets the banner in Turkish, even if the page says it is in another language, as long as Turkish is one of your banner's languages (or IAB TCF is on). A language the visitor picks in the banner, or one in the URL path, still comes first.

Visitors in Quebec get the banner in French when French is one of your banner's languages (or IAB TCF is on), as Quebec's Charter of the French language and Law 25 expect. Here too, a language the visitor picks in the banner, or one in the URL path, comes first. Canada already asks for consent first.

Texts

In the Content tab, choose a language and edit:

  • Banner title and message
  • Accept All, Reject All, Manage Preferences and Save button labels
  • Category names and descriptions in the preference centre
  • Cookie list labels (Cookie, Duration, Description, Always Active)
  • Links to your privacy policy, cookie policy and Aydınlatma Metni (see below)
  • Blocked embeds: the text shown in place of a video, map or other embed that waits for consent (see below)

Okito ships default banner messages for the GDPR template in English, Turkish, German, French, Spanish and Italian (KVKK wording in Turkish and English), and titles and button labels in 50+ languages. Adapt the defaults to your own processing and privacy policy.

In Content → Links, enter the full addresses (starting with https://) of:

  • Privacy policy: shown to every visitor under the banner text, the US State Laws notice included. Under the GDPR this is where visitors find your privacy notice; the default GDPR text refers to it.
  • Cookie policy (optional): shown to every visitor after the privacy policy link, as "Cookie Policy" in the visitor's language ("Çerez Politikası" in Turkish).
  • Aydınlatma Metni: only on a website whose country is Türkiye. Visitors in Türkiye get the KVKK text, and this link before the privacy policy link, as "Aydınlatma Metni" in Turkish ("Disclosure Notice" in English).

Like the texts, the links belong to the language you are editing, so each language can link to its own page. A language whose link is empty uses the default language's link. The Aydınlatma Metni is usually only in Turkish, so entering it in one language is enough: every language uses it.

The preference window shows the same links (the classic window, the design themes' and IAB TCF's). The links open in a new tab and use the visitor's language for the privacy policy label. An address that doesn't start with http:// or https:// is not shown. The Banner Builder preview shows them as the banner will.

With Show Google Privacy Policy on (Content → Preference Centre), the preference window also shows a Google Privacy Policy link after yours, in the visitor's language. It opens Google's page on how Google uses information from sites that use its services (business.safety.google/privacy). The setting applies to every language. The first layer doesn't show this link.

In mobile apps, the Okito SDK banner shows the same links in the app's language, the Aydınlatma Metni when the app's country in Okito is Türkiye and the device's region is Türkiye. A privacy policy address passed to the SDK in the app's code is used instead of the dashboard's.

Blocked embeds placeholder

Videos, maps and other embeds (YouTube, Vimeo, Google Maps and others; see Embedded videos, maps and posts) load only after the visitor allows their cookies. Until then a box stands in their place, with a message and a button that opens the cookie settings.

In Content → Blocked embeds you can replace both texts for the language you are editing:

  • Message: up to 300 characters. {name} is replaced with the name of the service, for example "Watch this video once you allow its cookies." becomes "Watch this YouTube video once you allow its cookies."
  • Button: up to 50 characters.

Leave a field empty to keep the default, which is translated into every language the banner supports; the field shows it in grey. The texts are plain text: HTML is not applied. In the Shopify app, the same fields are in Banner Build → Content → Blocked embeds.

Web addresses that start with https:// in the banner message also become links automatically.

IAB TCF texts

When IAB TCF is on, the banner uses IAB Europe's official texts and translations for purposes, features and vendors. These fields are locked in Banner Builder so the texts can't drift from the official wording.

If you use Google consent mode without IAB TCF, the Content tab recommends the Google Consent Mode template. See Google Consent Mode banner template.