Skip to main content

​
Email Localization

Sequenzy lets you author an email in one primary language and keep extra localized variants alongside it. You configure localization at the company level, then each email template can store per-locale variants that Sequenzy uses at send time.

​
How It Works

  1. You set a primary language for the company.
  2. You add supported locales such as es, fr, or pt-BR.
  3. You choose which subscriber custom attribute contains the locale value.
  4. You optionally map raw attribute values like spanish or pt_BR to normalized locale codes.
  5. Sequenzy resolves the recipient locale at send time and picks the best matching localized variant.

​
Company-Level Settings

Localization settings live on the company and apply to campaigns, automations, transactional template sends, and A/B test variants. You can configure:
  • Primary language and text direction: The language your emails are written in and whether new emails default to left-to-right or right-to-left.
  • Supported locales: The set of languages you want to maintain for email.
  • Fallback locale: The locale Sequenzy should use when a subscriber value does not match.
  • Subscriber locale attribute: The custom attribute key to read at send time, including dot-paths like profile.locale.
  • Value mappings: Raw subscriber values mapped to normalized locales, for example spanish -> es.
  • Auto-sync mode: Whether localized variants sync only manually or automatically when the source language changes.

​
Custom Locale Codes

If the locale you need is not in the language picker, you can enter a standard locale code directly. Use a two- or three-letter language code with optional script, region, or variant subtags, for example:
  • fr-CA for Canadian French
  • sr-Latn for Serbian written in Latin script
  • en-AU for Australian English
Primary locale codes can contain up to 10 characters. Additional supported locale codes can contain up to 32 characters. Sequenzy accepts either hyphens or underscores and saves the canonical form, so pt_BR becomes pt-BR. Deprecated language aliases also resolve to their modern codes, such as iw to he and tl to fil. Existing localized variants stored under an older alias continue to work and appear under the modern locale throughout the app and developer tools.

​
Per-Email Variants

Every email keeps its primary version as the source of truth. Additional locales are stored as localized variants with their own:
  • Subject
  • Preview text
  • Block content
  • Sync status
  • Last sync time
  • Last sync error

​
Sync Status

Localized variants move through four statuses:
  • synced: The locale matches the current primary-language source.
  • stale: The primary email changed and this locale needs to be refreshed.
  • syncing: Sequenzy is currently generating or refreshing the locale.
  • failed: The sync attempt failed and kept the previous content.

​
Send-Time Locale Resolution

When Sequenzy sends an email, it:
  1. Reads the configured subscriber attribute.
  2. Normalizes and maps the value to a locale.
  3. Tries an exact locale match such as pt-BR.
  4. Falls back to a base locale match such as pt.
  5. Falls back again to your configured fallback locale.
  6. Uses the primary language if no localized variant is available.

​
AI Sync

When you sync a locale, Sequenzy translates the human-readable content while preserving the email structure. The sync keeps:
  • Block IDs and block order
  • Styles and layout
  • Links and tracking settings
  • Merge tags such as {{FIRST_NAME}}
  • HTML tags inside rich text
Only visible copy is translated.

​
API, CLI, And MCP Access

Developer tools can inspect localized variants, store caller-supplied translations, and explicitly queue AI translation.

​
CLI

​
MCP

  • get_company returns the effective localization settings for a company.
  • list_templates returns template-level localization status by locale.
  • get_template returns the full localized variants for a template.
  • set_template_localization stores a caller-supplied localized variant.
  • sync_template_localizations queues AI translation for selected or all enabled non-primary locales.
  • sequenzy://company exposes the currently selected company as a read-only resource.

​
REST API

  • PUT /api/v1/templates/{templateId}/localizations/{locale} creates or replaces a localized variant using supplied HTML or Sequenzy blocks.
  • POST /api/v1/templates/{templateId}/localizations/sync queues AI translation. Omit locales from the JSON body to sync every enabled non-primary locale.

​
Notes

  • Direct transactional sends that provide raw subject and HTML are not localized automatically. Template-based sends are.
  • A localized variant can be edited manually, but any primary-language change marks it as stale until you sync it again.
  • A/B test variants maintain their own localized copies separate from the base email template.