40+ Languages: Global Consent Banner Localization

## The Lost Japanese Market A SaaS company expanded into Japan. They localized their product, hired Japanese support staff, and ran targeted advertising. Sign-ups came in. But conversion to paid was 40% lower than other markets. User research revealed the problem: the cookie consent banner. It appeared in English. Japanese users—particularly enterprise buyers—saw a foreign-language legal prompt and hesitated. Some bounced immediately. Others proceeded but trusted the product less. Localizing the consent banner took one hour. Conversion rates normalized within a month. The revenue impact: ¥180 million over the following year. Language isn't just courtesy. It's conversion. ## Why Language Matters for Consent ### Legal Validity GDPR requires that consent be informed. Information must be provided in clear, plain language. For many users, that means their native language. Some DPAs have explicitly stated that consent banners should match the website's primary language. Showing English-only banners to German visitors is a compliance risk. ### User Trust A consent banner is often the first interaction with your brand. A professional, localized experience signals that you take privacy seriously—and that you respect your visitors. ### Conversion Impact We've seen consistently that localized experiences convert better. A consent banner in the wrong language creates friction at the worst possible moment—before users have engaged with your content. ## 40+ Languages Supported ### European Union (Official Languages) | Language | Code | Script | |----------|------|--------| | English | en | Latin | | German | de | Latin | | French | fr | Latin | | Spanish | es | Latin | | Italian | it | Latin | | Portuguese | pt | Latin | | Dutch | nl | Latin | | Polish | pl | Latin | | Romanian | ro | Latin | | Czech | cs | Latin | | Greek | el | Greek | | Hungarian | hu | Latin | | Swedish | sv | Latin | | Danish | da | Latin | | Finnish | fi | Latin | | Slovak | sk | Latin | | Bulgarian | bg | Cyrillic | | Croatian | hr | Latin | | Slovenian | sl | Latin | | Lithuanian | lt | Latin | | Latvian | lv | Latin | | Estonian | et | Latin | | Maltese | mt | Latin | | Irish | ga | Latin | ### European (Non-EU) | Language | Code | Script | |----------|------|--------| | Norwegian | no | Latin | | Ukrainian | uk | Cyrillic | | Russian | ru | Cyrillic | | Serbian | sr | Cyrillic | | Turkish | tr | Latin | ### Asian Languages | Language | Code | Script | |----------|------|--------| | Japanese | ja | Japanese | | Chinese (Simplified) | zh-CN | Chinese | | Chinese (Traditional) | zh-TW | Chinese | | Korean | ko | Korean | | Thai | th | Thai | | Vietnamese | vi | Latin | | Indonesian | id | Latin | | Malay | ms | Latin | | Hindi | hi | Devanagari | | Bengali | bn | Bengali | ### Middle Eastern (RTL) | Language | Code | Script | |----------|------|--------| | Arabic | ar | Arabic (RTL) | | Hebrew | he | Hebrew (RTL) | ## Right-to-Left (RTL) Support ### What RTL Means Arabic and Hebrew read right-to-left. This affects: - Text alignment - Button positioning - Layout flow - Icon orientation A banner that looks professional in English can look broken in Arabic if RTL isn't properly implemented. ### Our RTL Implementation Our widget automatically: - Detects RTL languages - Flips layout direction - Mirrors UI elements - Adjusts spacing and alignment - Positions buttons correctly ### RTL Example **English (LTR):** ``` [Cookie icon] We use cookies... [Reject] [Accept] ``` **Arabic (RTL):** ``` [قبول] [رفض] ...نستخدم ملفات تعريف الارتباط [أيقونة] ``` The entire interface mirrors while maintaining usability. ## Automatic Language Detection ### Browser-Based Detection GetCookies reads the browser's language preference: ```javascript navigator.language // "ja-JP" navigator.languages // ["ja-JP", "ja", "en-US", "en"] ``` The widget matches against supported languages and displays the best fit. ### Fallback Logic 1. Check exact match (e.g., `pt-BR`) 2. Check language without region (e.g., `pt`) 3. Fall back to configured default 4. Ultimate fallback: English ### Manual Override Force a specific language: ```javascript window.getCookieConfig = { domainId: 'YOUR_DOMAIN_ID', language: 'de' // Always German }; ``` ### URL-Based Detection For multi-language sites with URL patterns: ```javascript // Auto-detect from URL: example.com/fr/about const pathLang = window.location.pathname.split('/')[1]; const supportedLangs = ['en', 'fr', 'de', 'es']; window.getCookieConfig = { domainId: 'YOUR_DOMAIN_ID', language: supportedLangs.includes(pathLang) ? pathLang : 'en' }; ``` ## Translation Quality ### Professional Translations All languages have been professionally translated by native speakers with legal/privacy expertise. We don't use machine translation for core consent text. ### Legal Accuracy Our translations maintain legal meaning: - "Consent" vs "Agreement" nuances - "Personal data" vs "Information" distinctions - Regulatory terminology accuracy ### Cultural Adaptation Beyond translation, we localize: - Formal vs informal address (Sie vs Du) - Cultural preferences for directness - Regional privacy expectations ## Customizing Translations ### Override Specific Strings For all languages: ```javascript window.getCookieConfig = { domainId: 'YOUR_DOMAIN_ID', translations: { en: { bannerTitle: 'Your Custom Title', acceptAll: 'I Agree' }, de: { bannerTitle: 'Ihr Angepasster Titel', acceptAll: 'Ich Stimme Zu' } } }; ``` ### Add Custom Languages Contact us to add languages not in our default set. ## Multi-Language Site Implementation ### Subdomain Pattern Different languages on different subdomains: ```javascript // en.example.com, de.example.com, fr.example.com const subdomain = window.location.host.split('.')[0]; const langMap = { en: 'en', de: 'de', fr: 'fr' }; window.getCookieConfig = { domainId: 'YOUR_DOMAIN_ID', language: langMap[subdomain] || 'en' }; ``` ### CMS Integration **WordPress (WPML/Polylang):** ```php ``` **Next.js (next-i18next):** ```jsx const { i18n } = useTranslation(); window.getCookieConfig = { domainId: 'YOUR_DOMAIN_ID', language: i18n.language }; ``` ## Language-Specific Compliance ### German (DSGVO) Our German translations use proper DSGVO terminology: - "Einwilligung" (consent) - "Verantwortlicher" (data controller) - "Betroffenenrechte" (data subject rights) ### French (CNIL) Our French translations align with CNIL guidance: - "Consentement" terminology - Proper "Continuer sans accepter" option - Clear rejection phrasing ### Nordic Languages Our Scandinavian translations reflect cultural directness and high privacy expectations. ## Analytics by Language Track consent behavior across languages: ### Dashboard Metrics - Consent rate by language - Interaction time by language - Category preferences by region ### Insights Common patterns we've observed: - German users: Higher reject rates - French users: More use of granular settings - US English users: Higher accept rates - Japanese users: Longer decision times Use these insights to optimize your consent experience. ## Implementation Checklist ### Basic Setup - [ ] Enable auto-detection in configuration - [ ] Set appropriate default language - [ ] Test banner in target languages - [ ] Verify RTL for Arabic/Hebrew if used ### Advanced Setup - [ ] Integrate with CMS language detection - [ ] Customize key translations if needed - [ ] Set up language-specific analytics - [ ] Test on international user devices ### Quality Assurance - [ ] Native speaker review of key languages - [ ] RTL visual testing - [ ] Mobile responsiveness per language - [ ] Character length verification (German is verbose!) ## Getting Started 1. Configure your domain in GetCookies dashboard 2. Enable auto-language detection (default: on) 3. Test by changing browser language 4. Customize translations if needed 5. Monitor language-specific consent rates Global business requires global consent. One widget, 40+ languages, zero translation management overhead.