Localization lets you create multiple language versions of your funnel that automatically display based on your visitors’ location and browser language. Studies show conversion rates improve by up to 70% when users see content in their native language.
Language switcher in Visual Editor

How Localization Works

FunnelFox automatically detects the best locale for each visitor using:
  1. Geographic location (IP-based country detection)
  2. Browser language (Accept-Language headers)
The system then matches visitors to your configured locales, falling back to your default locale if no match is found.
Important: Localized content is part of your funnel’s static build. You must republish after making localization changes for them to go live.

Creating Locales

Navigate to your funnel’s Locales page from the dashboard to manage translations.
Locales management page

Add a New Locale

  1. Click Add locale button
  2. Select Country (or use “Europe” for EU-wide targeting)
  3. Select Language
  4. Optionally enable catch-all for broader matching
  5. Choose whether to Translate with AI for instant translation
Creating a new locale

Locale Matching Priority

FunnelFox matches visitors to locales in this order:
  1. Exact match: Country + Language (e.g., Germany + German)
  2. Country with any language: Country match + catch-all language
  3. Language in any country: Catch-all country + language match
  4. Broad catch-all: Both country and language set to catch-all
  5. Default locale: Used when no other rules match
Pro tip: Use “Europe” as a country to target all 27 EU countries with one locale. Perfect for unified pricing or GDPR-specific content.

Managing Translations

What Can Be Localized

Can change:
  • All text content (headlines, paragraphs, buttons)
  • Images and media files
  • Input placeholders and labels
  • Option lists in dropdowns/radio buttons
  • Error messages
  • Meta tags and SEO content
Cannot change:
  • Page structure or flow
  • Number of elements
  • Element types or positions
  • Actions and triggers
  • Form field requirements

Editing in the Visual Editor

Switch between locales using the globe icon in the editor toolbar:
Locale switcher in editor
When editing a non-default locale:
  • Elements show a blue outline indicating they’re localizable
  • Structural changes are disabled
  • Only content modifications are allowed
Changes to the default locale’s structure automatically apply to all other locales. Be careful when adding or removing elements in the default locale.

AI Translation

FunnelFox includes built-in AI translation for quick localization:

During Locale Creation

Enable “Translate with AI” when creating a new locale for instant translation of all content.

From the Locales Page

Click Translate with AI on any existing locale to retranslate all content.
AI translation takes 1-2 minutes depending on funnel size. The page shows “Processing translation with AI…” during this time. You can navigate away and return later.

Translation Quality Tips

  • Review AI translations before publishing
  • Pay special attention to:
    • Brand names and product titles
    • Technical terms and acronyms
    • Calls-to-action (cultural adaptation needed)
    • Legal disclaimers and compliance text
    • Pricing and currency symbols

Import/Export Workflow

For professional translations or bulk editing, use the import/export feature:

Export for Translation

  1. Click Export from the Locales page
  2. Receive a TSV (Tab-Separated Values) file
  3. Share with translators or translation services

TSV File Structure

Key                                             🌐 Default         🇩🇪 Germany • DE
screens.welcome.elements.heading.props.content  Welcome!          Willkommen!
screens.welcome.elements.button.props.text      Get Started       Loslegen
Each row contains:
  • Key: Unique identifier (don’t modify)
  • Default column: Original text
  • Locale columns: Translated text for each locale

Import Translations

  1. Ensure TSV maintains the exact structure
  2. Click Import and select your file
  3. Review changes in the editor
  4. Republish to make changes live
Import overwrites all existing translations for included locales. Always backup by exporting first.

Catch-All Locales

Catch-all settings let you create flexible matching rules:

Use Cases

Language catch-all: Show Spanish content to all Spanish speakers regardless of country
Country: Spain
Language: Spanish (catch-all enabled)
Result: Matches visitors from any country with Spanish browser language
Country catch-all: Show content to all UK visitors regardless of language
Country: United Kingdom (catch-all enabled)
Language: English
Result: Matches all UK visitors, even with non-English browsers
Ultimate fallback: Create a broad safety net
Country: Catch-all
Language: Catch-all
Result: Matches anyone not caught by other rules (before default)

Overriding Locale via URL

You can override the automatic locale detection by passing an ff-locale parameter in the URL query string. This is useful for:
  • Testing different language versions without VPN
  • Sharing direct links to specific language versions
  • Quality assurance and review workflows
  • Customer support scenarios

Using the Locale Parameter

Add ?ff-locale= followed by the locale code to any funnel URL:
https://example.fnlfx.com/welcome?ff-locale=de-DE
https://example.fnlfx.com/welcome?ff-locale=es-ES
https://example.fnlfx.com/welcome?ff-locale=fr-FR
The ff-locale parameter accepts standard ISO language codes in the format:
  • language-COUNTRY (e.g., en-US, de-DE, fr-FR)
  • language only (e.g., en, de, fr)
The ff-locale parameter must match one of your configured locales. If an invalid or non-existent locale is provided, FunnelFox falls back to automatic detection.

Parameter Persistence

When a locale is set via URL parameter:
  • It overrides geographic and browser language detection
  • The preference persists throughout the funnel session
  • Subsequent page navigations maintain the selected locale
  • The parameter doesn’t need to be included on every page

Examples

Direct link to German version:
https://your-project.fnlfx.com/signup?ff-locale=de-DE
Append to existing parameters:
https://your-project.fnlfx.com/offer?utm_source=email&ff-locale=fr-FR
Testing multiple locales quickly:
# Open multiple browser tabs with different locales
open https://example.fnlfx.com/?ff-locale=en-US
open https://example.fnlfx.com/?ff-locale=de-DE
open https://example.fnlfx.com/?ff-locale=es-ES

Testing Locales

With the locale URL parameter and other methods, you have multiple ways to test:

Test Different Locales

  1. URL Parameter: Add ?ff-locale=xx-XX to force a specific locale
  2. Use VPN: Connect from different countries to trigger geo-detection
  3. Change browser language: Modify browser’s language preferences
  4. Use different devices: Test with colleagues in other locations
  5. Browser extensions: Use header modification tools to change Accept-Language

Preview Mode Testing

Preview mode uses the same locale detection as production, including support for the locale URL parameter. Your detected locale in preview helps verify the experience visitors will see.

Best Practices

Design Considerations

Plan for Text Expansion

German and French text is often 30% longer than English. Design with flexible layouts that accommodate varying text lengths.

Use Neutral Images

Choose images without embedded text or use localized versions to avoid language mismatches.

Test Currency Display

Ensure prices display correctly with appropriate currency symbols and decimal separators for each locale.

Respect Cultural Norms

Colors, imagery, and messaging that work in one culture may not resonate or could offend in another.

Performance Tips

  • Start with your most important markets
  • Use analytics to identify visitor languages
  • Prioritize locales with highest traffic potential
  • Consider regional catch-all locales for smaller markets

Maintaining Consistency

  1. Establish glossary: Keep consistent translations for key terms
  2. Document tone: Maintain brand voice across languages
  3. Regular reviews: Update translations when default content changes
  4. Version control: Export TSV files before major updates

Common Patterns

European Union Targeting

Country: Europe
Language: English
Use case: Single pricing/terms for all EU countries

Spanish-Speaking Markets

Locale 1: Spain + Spanish
Locale 2: Mexico + Spanish  
Locale 3: Catch-all + Spanish (for other Spanish speakers)

English Variants

Locale 1: United States + English (default)
Locale 2: United Kingdom + English (British spelling/terms)
Locale 3: Australia + English (local terminology)

Troubleshooting

Technical Reference

Locale Detection Data

Your webhooks and API responses include:
  • locale: Full locale name (e.g., “Germany • DE”)
  • locale_code: ISO format (e.g., “de-DE”)

Europe Country Codes

The “Europe” country option includes all 27 EU member states: AT, BE, BG, HR, CY, CZ, DK, EE, FI, FR, DE, GR, HU, IE, IT, LV, LT, LU, MT, NL, PL, PT, RO, SK, SI, ES, SE

Next Steps