Texts and Translations Set Up
This Technical Setup Guide provides the configuration steps required to manage and standardize Text and Translation across all loyalty channels within the TRIFFT Cockpit.
| Topic / function | Text and Translation |
|---|---|
| Audience | CRM / Marketing Ops / Implementation |
| Goal | Provide step-by-step setup for localizing content and system labels across all channels |
| Prereq systems | TRIFFT Cockpit, configured Project Languages |
What you will learn
This guide covers how to manage multi-language support in the TRIFFT Cockpit, including localizing marketing content (News, Deals) and standardizing system-level UI text (App labels, button text) to ensure a consistent experience across the Mobile App and Web Portal.
Prerequisites
- Access: Ensure you have the Admin or Editor role to access content modules and project settings.
- Project Configuration: Confirm that all required languages (e.g., English, German, Czech) are activated in Project Settings.
- Source Content: Complete the "Primary Language" version of your News, Deal, or Page before starting translations.
Step-by-step setup
- Enable Project Languages:
- Navigate to Settings > Project Settings.
- Add all locales your program must support to ensure the translation tabs appear in content modules.
- Localize Marketing Content:
- Open any content item (e.g., Content > News or Deals).
- Navigate to the Translations tab at the top of the editor.
- Select a target language from the list.
- Input the localized Title, Lead Text, and Article Body.
- Translate System UI Labels:
- Go to Settings > Translations (Global Labels).
- Search for specific UI keys such as "Points," "Total Balance," or "Log In".
- Provide the translation for each active language to ensure the App and Web Portal interfaces are fully localized.
- Localize Legal Pages:
- Navigate to Content > Pages.
- Use the Translations tab to provide the localized version of your Terms & Conditions or Privacy Policy.
- Configure Communication Templates:
- In the Communication modules (Push/Email), ensure localized versions of the message body and subject line are provided for each member segment's language preference.
- Set Fallback Logic:
- Confirm which language is set as the Default; this version will be shown if a translation is missing for a member's specific locale.
- Preview and Save:
- Toggle between languages in the preview pane to verify formatting and click Save Changes.
Configuration checklist
- Translation Coverage: All active languages have localized values for mandatory fields like Titles and CTAs.
- System Label Audit: Core app interface labels (e.g., "History," "Wallet") are translated in the Global Labels section.
- Fallback Verification: The "Default Language" is correctly assigned to prevent blank content for unsupported locales.
- Formatting Consistency: Rich text formatting (bolding, links) is applied consistently across all translated versions of an article.
- Legal Alignment: Localized "Terms & Conditions" pages are accurately mapped and accessible in the App/Web Portal menus.
Updated 3 days ago
Did this page help you?
