Skip to main content

Pre-Translate Locked Modules for Translated Assets

Translate a locked module once. Every translated email or landing page that uses it shows the right language.

Note: This feature is currently in Beta testing. Please reach out to tiffany@knak.com if you would like to participate.

Overview

A locked module is a module that no one can change inside an asset. Headers and footers are common examples. When you translate an asset, Knak skips locked modules. They stay in the original language.

Module pre-translation fixes this. Translate the locked module in the module builder. Each translation is called a variant. When you translate an asset later, Knak uses the matching variant.

Benefits

  • Translate shared content once instead of in every asset.

  • Keep locked content consistent in every language.

  • Translate whole assets without missing headers or footers.

Demo Video

Before You Begin

  • You need the role permission to edit modules. This gives you access to Admin > Modules.

  • Your account needs Knak Translations or a connected translation integration, such as Smartling or TransPerfect.

Note: Only globally locked modules can be translated in the module builder. A globally locked module has Locked turned on in its own settings, so it is locked in every asset that uses it.

If the module is not locked, the Translations panel shows a warning instead of the translation options.

Translate a Locked Module

Step 1: Lock and Publish the Module

  1. Open your module from Admin > Modules.

  2. Turn on Locked in the Settings panel. Click Lock Module to confirm.

  3. Click Not Published at the top right, or open the Actions menu.

  4. Click Publish.

    Applying a global lock to a module and publishing.

Note: Locking applies the module to every asset and theme that uses it. Any custom content in those assets is replaced. Learn more about how to Use Globally Locked Modules to Exclude Content from Translation.

Step 2: Request a Translation

  1. Click the Translations icon in the left toolbar of the module builder.

  2. Click Translate now.

    The Translations panel showing Ready for Translation? and the Translate now button.

  3. Choose how to translate the module:

    • To use AI translation, manual translation, or an XLIFF file, click Use Knak Translations. Then follow steps 4 to 7.

    • To use a connected integration, such as Smartling or TransPerfect, click Select next to it. Then follow the translation flow for that integration.

    Request translation screen displaying translation options.

  4. Check the Source Language. This is the language the module is written in. Click Continue.

  5. Check the box next to each language you want. Click Next: Sources.

  6. Pick a translation source for each language: Manual Translation, AI Translation, or Upload Xliff. Click Next: Confirmation.

  7. Review the summary. Click Submit Request.

Each language now shows in the Translations panel with the status In progress.

The Translations panel listing French and German variants marked In progress.

Tip: Use an outside translation tool? Click Download Base Module XLIFF. XML Localization Interchange File Format (XLIFF) is a standard file that translation tools can read.

Publish Translated Modules

Translating a module does not publish it. Your assets only use published translations.

Publish the Base Module and All Variants

  1. Open the base module.

  2. Click Not Published at the top right, or open the Actions menu.

  3. Click Publish.

Publish One Variant

  1. Open the variant. Use either option:

    • Click the variant option at the top of the module. Choose the language from the dropdown.

    • Click a completed language in the Translations panel.

  2. Click Not Published at the top right, or open the Actions menu.

  3. Click Publish. Only that language is published.

Important: Edits to a variant only reach your assets after you publish that variant.

Apply Changes from the Base Module

The base module is the original module in its first language. When you change its structure, its variants become out of date. Structure means the layout, such as sections, rows, and content blocks. An indicator on the base module shows which variants need an update.

  1. Open the base module.

  2. Find the indicator that shows out-of-date variants.

    The base module showing the out-of-date variants indicator.

  3. Click the indicator and update the variants to apply the changes to each variant.

  4. Publish the base module again so your assets use the updated variants.

Note: Only structural changes carry over. The translated text in each variant stays the same.

How Translated Modules Appear in Your Assets

When you translate an email or landing page, Knak checks each locked module. It looks for a variant in the target language. It matches on the language code, such as fr-CA.

Module status

What shows in the translated asset

Has a published variant in the target language

The translated variant

Has a variant, but the latest version is not published

The last published version of that variant

Has no published variant in the target language

The base module, in its original language

Example

You translate an email into French and German. The email has a locked footer.

  • Before pre-translation: The email body is translated. The footer stays in English.

  • After pre-translation: Translate the footer into French and German in the module builder. Publish it. Translate the email again. The footer now shows in French and German.

Review Your Assets Before You Sync

If a locked module has no matching published variant, it shows in its original language. Knak does not stop you from syncing or sending when this happens.

Before you sync or send, preview each translated asset. Check that every locked module shows in the right language.

Important: Language codes must match exactly. A French (Canada) fr-CA email only uses a fr-CA variant. If the module only has a French fr variant, the module shows in its original language.

Things to Know

  • Only globally locked modules can be translated. Unlocked modules are translated as part of the asset, the same as before.

  • Translated modules cannot be unlocked. Delete the translations first. Or clone the module and unlock the clone.

  • Language codes must match exactly. A fr-CA asset uses a fr-CA variant. It does not use a fr variant instead.

  • Cloning creates a new base module. When you clone a module or variant, choose to clone the base only or the base with its translations.

  • Download module HTML exports one version. Only the module or variant you are viewing is exported.

Best Practices

Pre-Translate Shared, Fixed Content

Module pre-translation works best for content that rarely changes between campaigns.

Recommended

  • Headers and footers.

  • Legal disclaimers and compliance text.

  • Brand-approved standard text.

Avoid

  • Modules that need edits for each campaign.

Publish Before You Translate Assets

Assets only use published variants. Publish the base module and its variants first. Then translate your assets.

Use the Same Language Codes Everywhere

Translate modules into the exact language codes your assets use. This keeps modules from showing in the original language.

Need more help? Contact support via live chat within Knak using the chat bubble in the bottom right corner or email support@knak.com.

Related Articles
Did this answer your question?