Salesforce Marketing Cloud email in several languages and markets.

By Alexander Andersson · Updated 1 Nov 2026 · Salesforce's docs checked 1 Nov 2026

Which Salesforce Marketing Cloud does this page cover?

Both, kept apart, because they work differently. Marketing Cloud Next runs on the Salesforce platform: data comes through Data 360, content lives in Salesforce CMS, journeys run in Flow Builder, with Agentforce along the way [1]. Salesforce lists it for Enterprise and Unlimited Editions with the Marketing Cloud Growth or Advanced Edition [2]. Marketing Cloud Engagement is the product formerly called Marketing Cloud, with Email Studio and Content Builder [1][8][10]. Caliber's integration is with Marketing Cloud Next; the Engagement sections are here because many teams still send from it.

How do language variants work in Marketing Cloud Next?

You write the email once in the default language and add a variant per language. First, add each language to the marketing workspace under Manage, then Languages; the default language stays selected and locked. In Email Builder, the Language Variants icon lists the default and each workspace language. Translate Variant translates the copy, image alt text included, and you review it in the components view, Code View or Text View [3].

Every variant inherits layout, style and data source updates from the default variant [3]. That keeps the build to one email; it also means a structural change reaches every language at once. Adding languages and editing variants needs the Marketing Cloud Manager permission set and a CMS workspace contributor role [3].

AI translation runs through Agentforce. You can ask the agent in the Agentforce panel to translate a variant. Salesforce notes that upgrading to Winter '27 does not add the Translate Text Content action to agents built in Summer '26 or earlier: you add it yourself in Agentforce Builder [3]. In the agentic content workspace, Translate generates a variant for each language you select, and you edit or paste over the result [4].

Can you send Marketing Cloud Next emails to a translation agency?

Yes, as XLIFF files. Under Manage, then Translations, Export produces the files; you download them from Job Statuses. The translator keeps the file structure and identifiers unchanged, and you import the files as a .zip. Import overwrites any existing translations, and fixes after import happen in Email Builder [3]. Export and import need the Manage Translation and Create Documents permissions [3].

Two rules from Salesforce CMS shape the schedule. Content marked Ready for Translation is locked against changes, and translations import only while the original stays in that status [5]. And a new draft of a published email archives the previous version with its translations, so the new draft needs translating again [3]. Plan the copy freeze before the export, not after.

How does Marketing Cloud Engagement handle several languages?

With dynamic content, AMPscript, and one email per encoding. Dynamic content in Content Builder shows content by rules on subscriber attributes or data extension columns. Each rule has an attribute, a value, an operator and content. Subscribers who match no rule get the default content, and dynamic content works in every email type except text-only [8]. Empty attribute values are evaluated as zero, so a subscriber with no language value falls through to the default [8]. If a data extension column has the same name as a profile attribute, the data extension wins [8].

For content chosen in code, AMPscript's ContentBlockByKey() returns a Content Builder block by its key, with a status code you can use to show fallback content when the block is missing [9]. The same function works in Marketing Cloud Next since the Summer '26 release, where it reads the most recently published block from Salesforce CMS [9].

Encoding is the Engagement-specific trap. With International Sends, each email has one language encoding; Salesforce recommends UTF-8 for most international audiences, and existing emails default to US-ASCII [10]. Its International Sends guidance says each email can use only one encoding, so Japanese and Chinese cannot share one email [11]. The standard Profile Center, Subscription Center and unsubscribe pages come in 21 languages, Danish, Finnish, Norwegian and Swedish among them, chosen by the subscriber's browser language rather than the email's [10].

How do you keep legal lines and footers per market?

In Marketing Cloud Next, the consent details are merge fields: Physical Address inserts your organization's address from Salesforce Setup, and the Unsubscribe and Preference Manager links resolve to URLs at send time [7]. That is one address for the org. A brand with a company per market, such as an AS in Norway and an Oy in Finland, needs the company line written into each language variant or a dynamic content variation, not the Physical Address field alone.

In Marketing Cloud Engagement, Salesforce recommends language-specific content headers and footers for all international emails, chosen through the delivery profile of a send definition or written into the template. Not every non-ASCII character works in those footers; Salesforce names double-byte characters such as Japanese, Chinese, Thai and Russian [11].

Either way, a legal line follows the market, not the language. Engagement's business units can mirror your organization's structure and control access to and sharing of content [12], which is one way to keep each market's footer in that market's hands.

One email with variants, or one email per market?

Language variants make one email cheap to build, but they do not make markets the same. Nordbite is a fictional demo brand. Its fixture has two markets, Norway and Finland, with two currencies and two scopes for its price-reduction rule. Mapped to Marketing Cloud Next:

The rule scope is where one email gets hard. A line such as "20% off this week" is a reduction claim in Finland's scope even with no product price on show, while Norway's scope applies only when prices appear. With variants, the Finnish copy can drop the line, but a change to the shared layout or data source still reaches Finland [3]. The scopes are fixture data, not legal advice.

Where do reviews happen?

In Marketing Cloud Next, preview each language variant before you publish the email [3]. Dynamic content adds a second axis: a recipient who matches no targeting rule gets the default variation, and an email or landing page holds up to 25 personalization points, with subject line and preheader counting as one [6]. Targeting rules can use attributes, related attributes, calculated insights or segment membership [6].

One question the Next articles cited here leave open is how a send picks each recipient's language variant, and what a recipient with no language receives. Test that with real contacts in each market before the first live send.

Also on.

Klaviyo · Braze · Salesforce Marketing Cloud Next · Voyado · Customer.io · Iterable