Languages

Localize your donor experience into over 20 languages.

Fundraise Up’s localization features let you translate the donor experience into your supporters’ preferred languages.

Enabling localization

 
Link copied

You can enable and manage localization by going to Settings and selecting Localization from the side menu. Only the Dashboard’s Organization Administrator(s) can alter the organization’s localization settings. Learn more →

Supported languages

 
Link copied

Fundraise Up currently supports 23 locales:

Arabic (World) Hungarian
Chinese (Traditional) Italian
Chinese (Simplified) Japanese
Danish Korean
Dutch Norwegian
English (Canada) Polish
English (United Kingdom) Portuguese (Brazil)
English (United States) Portuguese (Portugal)
Finnish Russian
French (Canada) Spanish/Spanish (US)
French (France) Swedish
German

Our approach to localization

 
Link copied

Rather than using machine translation services, Fundraise Up uses native speakers of each language to provide professional and highly accurate translations of all our labels and content. Because our translations are done by humans, we’re also able to take into account region-specific dialects and cultural nuances.

Localization throughout the platform

 
Link copied

Fundraise Up’s localization tools are built into many components of the platform. The list of components that can be localized can be found below.

Localization into other languages is only available for supporter-facing texts (Checkout modal, Campaign Pages, emails, Donor Portal etc.). Organization-facing parts of the Fundraise Up platform, like our Dashboard, are always displayed in American English.

Checkout form

 
Link copied

The entire Checkout experience, as embedded in the Checkout modal and the Campaign Page, can be localized into any of our available languages. When localization is enabled in the organization’s account settings, the product labels in the Checkout form are automatically translated according to your settings. As for customizable content, such as the title and message on a Checkout modal Ask page — you will see default texts for each language, but you are free to add your own texts for each localization.

Elements

 
Link copied

The labels used in the Elements components are automatically translated if you choose to localize the user interface. For customizable content, you will see localized default texts, but you are free to add your own texts for each localization.

Donor Portal

 
Link copied

The Donor Portal is automatically translated to the language the supporter used during the checkout process. Within the Donor Portal, a supporter can choose a different preferred language. If a supporter changes their preferred language in their Donor Portal, this new preference is saved to their Supporter record.

Exports

 
Link copied

When you create an export template, you can include a file column to show the Supporter language. You have three options for how this preferred language is displayed:

  • Simple name: the general name of the language, without a dialect specified. For example: “English”
  • Name: the name of the language, including the dialect. For example: “English (USA)”
  • ISO code: the language’s alpha-2 code in the IOS system and its associated country. For example: “en-US.”

To include multiple language name formats in your export file, add the Supporter language file column to your template multiple times, and under Format you can change the columns to show different formats. Learn more about exports →

Emails

 
Link copied

When localization is enabled from your organization’s account settings, you’ll see a Localization tab also appear in the settings for emails (SettingsEmailsLocalization). You can add a From name and a standard footer for each of the languages you’ll be using (change between languages using the downward arrow next to the language name). You’ll also see all our default localized email content. You can use this default content, or add your own content for each language. Learn more about emails →

Designations

 
Link copied

To add localized versions of a pre-existing Designation, return to your organization’s main settings, and go to Designations in the side menu. Click the three dots to the right of the campaign that contains that designation option, and click Edit. Open the Localization tab and enter localized names for the Designation. You can localize the Designation to any of the interface languages pre-selected in your organization’s main settings.

When creating a new Designation, you choose a default language for that Designation and can add localized versions in the Localization window. Learn more →

Receipts

 
Link copied

The PDF receipts generated by Fundraise Up are always in the organization’s default language, as configured from the Localization page in your organization’s main settings. Even if a supporter completes a donation using the Checkout form in a language that isn’t the organization’s default, the receipt for their donation will be written in your organization’s default language. This is to ensure that receipts comply with the regulations set by the country where they are issued. Learn more about receipts →

In Canada, receipts must be provided in both English and French. For Canadian organizations, Fundraise Up displays the content of the receipt in both languages automatically.

Integrations

 
Link copied

For integrations that include the ability to add mapping rules, you can map three localization-related values from the donation object to the connected app.

  • supporter language iso code: this is the alpha-2 code in the IOS system and its associated country. For example: “en-US”.
  • supporter language name: this is the name of the language including the dialect. For example: “English (USA)”.
  • supporter language simple name: this is the general name of the language, without the dialect included. For example: “English”.

Multiple values (e.g. both the language’s simple name and the ISO code) can be mapped to a connected app by creating multiple mapping rules. Learn more →

Related article
Platform basics • Region-specific
features

 

In this article