Localization

Audryo sends each contact the email in their language. Today projects can use English and German. The Audryo app itself is in English.

How the language is chosen

1. The contact's locale field decides (en or de).
2. If that language is not enabled for the project, or the contact has no locale, the project's default language is used.

Set the enabled and default languages under Settings → General, and send locale with your contact data.

Language variants

Each email has one variant per enabled language. In the Emails library, they appear as EN / DE chips on the same card. Open a chip to edit that variant.

Campaigns fall back to the default language when a variant is missing. For anything you care about, publish both.

Translate

Translate in the editor drafts a new variant from an existing one. The result is a draft, never published automatically. Before you click Publish, have someone who reads the language check:

• tone and form of address (German: *du* or *Sie* — be consistent),
• product names and legal wording,
• that merge tags are unchanged, and
• the layout. German text is often about 30 % longer, so buttons and headlines may wrap.

Working with an agent? Ask it to write both languages directly instead of translating afterwards. See Design emails with your agent.

Footers and system emails

• Each language has its own shared footer. Click the footer on the canvas to edit it.
• The double opt-in email is a separate system email. Prepare it for each language you collect signups in under Settings → General.

What stays untranslated

Internal names (emails, audiences, Journeys, campaigns), tag names, field keys, and merge tag keys. {{ contact.first_name }} stays the same in every language; only the surrounding text changes.

Related

• The editor
• Journeys
• Contacts & events