Your competitor sends the same promotion to three markets and gets 2.5x more orders from the same audience sizes. It’s not about ad budget. They just didn’t send “Don’t miss out!” word-for-word translated as “Verpassen Sie es nicht!” in a newsletter using casual “du” to Munich customers who expect “Sie”, and they didn’t run a Valentine’s Day campaign to Brazil in February when the actual love holiday there is June 12.
According to CSA Research - a survey of 8,709 consumers across 29 countries:
76% of online consumers prefer buying products with information in their native language. 40% will never buy from websites in other languages - even if they can read English.
That’s not a “nice to have.” It’s direct conversion math: without localizing your email campaigns and push notifications, you’re deliberately cutting off 40% of potential customers in every market you enter.
But localization isn’t “translate the text and swap the image.” Here’s what actually needs to happen - and why most companies stop at 20% of the work.
Why text translation is only the beginning¶
When a marketer says “we localized the campaign,” it usually means: copy translated, subject line translated, same image. The remaining 80% is typically left undone.
Here’s the full list of what real email localization actually involves:
Text and subject line - what most teams do. But there’s a catch even here: translation isn’t the same as adaptation. “Check out our new arrivals” can be translated accurately and still sound stiff to a native speaker. Writing fresh in the target language beats word-for-word translation every time.
CTA (call-to-action) - the most commonly broken element. “Get Started,” “Grab your discount,” “Snag yours” - these are American marketing idioms with no natural equivalents in most languages. After “translation,” they read as either stiff (“Receive the beginning”) or meaningless. They need to be rewritten, not translated.
Register and tone - German B2C emails use “Sie” (formal you) by default unless the brand is explicitly youthful. Japanese baseline tone is far more formal than US. Brazil is the opposite - very conversational. Translation without register adjustment is a classic cause of low open rates in new markets.
Holiday dates - Valentine’s Day on February 14? Not in Brazil, where the love holiday (Dia dos Namorados) is June 12. Christmas email to Muslim audiences? That’s not just a miss - it’s an offense.
Date formats - 02/03/2025 means February 3 in the US and March 2 in the UK, Germany, or Ukraine. If you have a promotion deadline, use a written-out format (“2 March 2025”) or adapt to the local convention.
Currency and pricing - showing USD prices to EU audiences without conversion is friction. Customers stop to do the math instead of clicking.
Images - if your banner has embedded text, it doesn’t translate automatically. Every language version needs a separate image asset. Bigger problem: cultural mismatch. A Christmas tree in an email to UAE customers, or a swimwear image in messaging for Gulf markets, damages brand relationships.
Layout and text direction - Arabic and Hebrew require a full template rebuild (RTL - right to left). Without it, the entire layout looks broken.
The stats back this up. According to Smartlead.ai, localized email campaigns deliver +35% open rate and +56% CTR compared to the same English-only campaign. And 47% of subscribers decide whether to open based solely on the subject line - so a native-language subject is the single highest-leverage fix.
What specifically to adapt in an email campaign¶
Subject line and preheader¶
The subject line is the highest-leverage element: one line of text that determines open rates for the entire send. There are three levels of effort here.
Level 1 (minimum): translate the subject. Ensure it’s natural, not literal.
Level 2 (good): rewrite the subject for the audience’s psychology. American clickbait “You WON’T believe this deal” fails in Germany - “30% off winter collection, ends Friday” works better. Specific, no exclamation mark.
Level 3 (excellent): A/B test localized subject variants. Even between a “formal” and “informal” version in the same language, you’ll typically see 15-25% open rate differences.
The preheader (preview text after the subject) deserves the same attention. Most teams translate the subject and leave the preheader in English. The result: “Hi! 40% off… View this email in your browser” - it looks careless.
Technical note: optimal subject length is 36-50 characters. Mobile clips anything over 50. After translating to German or Polish, subjects routinely stretch to 60-70 characters - so start with a shorter source version to leave headroom.
CTA buttons and links¶
“Buy Now” → direct equivalent in most languages - works. But “Get in on it” → ? “Grab yours” → ? “Don’t sleep on this” → ?
These are American marketing idioms that don’t translate. Two options: either avoid them in the source copy (write “Shop now,” “See offer,” “Get 30% off” - these translate cleanly), or have a native speaker write the CTAs from scratch rather than translating them.
Specific note: aggressive urgency language (“Buy now! Limited time only!”) underperforms in Japan, South Korea, the Netherlands, and Germany. Softer urgency (“Available until Friday,” “Limited availability”) consistently gets better CTR in those markets.
Body copy¶
The rule here is simple: the simpler the source text, the better the translation. Short sentences, no idioms, no phrasal verbs - these translate cleanly.
Practical step before sending to translation: go through the copy and replace all phrasal verbs (check out → review, put up with → tolerate, sign up → register) and idioms with direct equivalents. This significantly improves machine translation quality and reduces post-editing cost.
Images and design¶
If your email has image banners with embedded text, every language version requires a separate image. Budget for this in production planning. For campaigns across 5+ languages, this is often the main production cost driver.
The alternative: place text over images via CSS/HTML instead of baking it into the image asset. One image serves all language versions, and the translated text renders on top.
Push notifications: technical limits and cultural nuances¶
Push is a separate channel with its own requirements. The hard character limits directly affect translation strategy.
Character limits by platform¶
According to SashiDo and CleverTap:
| Platform | Title (visible) | Body (visible) |
|---|---|---|
| iOS (collapsed view) | 25-50 characters | ~150 characters |
| iOS (expanded) | 25-50 characters | up to 178 characters |
| Android | up to 65 characters | up to 240 characters |
| Web push (Chrome) | ~50 characters | ~120 characters |
Collapsed view - notification sitting on the lock screen - is the primary viewing context. Most users don’t expand. They read what’s visible and either tap or swipe away.
The text expansion problem after translation¶
This is the technical issue almost no one thinks about when planning multilingual push campaigns.
Languages aren’t equal in volume. What happens when you translate 150 English characters:
| Language | Typical expansion | 150 English chars → |
|---|---|---|
| German | +20-30% | 180-195 characters |
| Portuguese (PT-BR) | +15-25% | 172-187 characters |
| Finnish | +30-50% | 195-225 characters |
| Spanish | +10-20% | 165-180 characters |
| Japanese | -30-40% | 90-105 characters |
| Chinese | -40-50% | 75-90 characters |
As SashiDo puts it:
“English might fit. German or Portuguese might not.” A 150-character English push body can become 200+ characters in German - exceeding iOS visible limits entirely.
Practical rule: when writing a push notification for a multilingual launch, write the source body shorter than you need - 80-100 characters - and leave expansion headroom for translated versions.
Emoji in push notifications: three rules¶
Emoji boost push open rates (various sources report +20-30%), but there are constraints.
Each emoji = 2 characters in most counting systems. If your limit is 150 characters and you have 5 emoji, you’re really left with ~140 for text.
New emoji = empty boxes on older devices. Unicode 13.0+ emoji (2020+) don’t render on Android 9 or older iOS versions. Your 🫶 becomes □ for a portion of your audience.
Emoji meaning varies by culture. 🙏 means “thank you” in the US. In Thailand, it’s “please.” In some contexts, it reads as a “high five.” Don’t assume universal meaning.
Safe approach: stick to Unicode 12.0 and earlier emoji sets, 1-2 per notification, only where the meaning is obvious without cultural context.
Market nuances: what you need to know by country¶
Germany¶
The most common mistake when adapting campaigns for Germany is tone. American marketing style (“Don’t miss out! Act now! This is HUGE!”) comes across as aggressive and unprofessional.
What works in Germany: - Formal “Sie” (not “du”) as the default, unless your product targets under-25s or the brand is explicitly casual - Concrete subjects: “30% off footwear - until Friday” not “Incredible news is waiting for you!” - Functional CTAs: “View collection,” “Place order” instead of “Grab it!,” “Don’t miss out!” - Send Tuesday-Thursday, 10:00-12:00 Berlin time (Sunday is dead for commercial email) - GDPR compliance: unsubscribe link is mandatory and readers do check
Japan¶
Japanese email marketing is its own context. A few key things.
Subject lines here run longer and more descriptive than short American-style punchy subjects. Japanese readers expect more context. And Japanese text contracts significantly compared to English (-40%), so you have more room for detail in your copy.
Aggressive urgency language (“Buy now! Only 2 hours left!”) reads as pressure and reduces trust. “Limited availability” or “Available until [date]” - without exclamation marks - works better.
Formal register is expected for most B2C categories. Don’t port the casual US tone.
Brazil¶
Two things that get missed constantly.
Valentine’s Day in Brazil is June 12 (Dia dos Namorados). Not February 14. If you’re running a Valentine’s Day campaign and targeting Brazil, you’re sending a holiday email in the wrong month. This happens across dozens of brands every year without fail.
Text expansion. Brazilian Portuguese expands text 15-25% compared to English - especially relevant for push notifications.
Tone here is very warm and conversational. Brazilian audiences expect a “human” brand voice with personal address.
Arabic-speaking markets and RTL languages¶
RTL (right-to-left) for Arabic and Hebrew isn’t just “translate the text.” It’s a full template rebuild: - Text alignment flips to right-left - Images and blocks mirror - Buttons and navigation shift to the opposite side
If your ESP doesn’t support RTL subject lines, Arabic text in the subject will render in reverse order - characters appear in the wrong sequence. Remarkety documents RTL subject support as a specific feature - it’s not a standard across all platforms.
One more: China has a legal requirement that commercial email subject lines must include an “AD” marker. Not optional - it’s the law.
Tools and workflow: three approaches¶
Approach 1: ESP with built-in localization (lowest-barrier start)¶
Klaviyo Smart Translations - the most accessible option for SMBs. Supports 60+ languages, built directly into the platform. Flow: select source language → choose target languages → review and edit machine translation → set fallback language for subscribers with unknown locale.
Integrates with Shopify Markets: automatically adapts product info, currency, and pricing by locale. Limitation: content must be finalized in the source language before translation starts - edits afterward trigger a full re-translation workflow.
Braze - enterprise level. Supports multilingual email and push via Connected Content. Integrates with TMS platforms (Crowdin, Phrase, Transifex). Clients include DoorDash, HBO, Burger King. Pricing is enterprise/custom.
Mailchimp - no native translation engine. You need manual geographic segmentation and separate content per language. Works if you’re running 2-3 languages with low volume.
Approach 2: TMS integration (for ongoing campaigns across 4+ languages)¶
A TMS (Translation Management System) centralizes the translation process and automates sync with your ESP.
Crowdin integrates with: Mailchimp, HubSpot, Braze, SendGrid, Figma, ActiveCampaign, Iterable. Flow: push source strings for translation → get localized versions back → automatic sync to your ESP.
Alternatives: Phrase (formerly Memsource), Transifex, Smartcat. The right choice depends on your ESP and CAT tools.
When it makes sense: if you’re running campaigns across 4+ languages regularly and the translation volume is significant. For one-off campaigns - TMS integration won’t pay for itself.
Approach 3: AI + post-editing (flexible and scalable)¶
The most common setup for teams without a dedicated TMS budget:
- Write the campaign in your source language, strip out idioms and phrasal verbs
- Translate with AI (DeepL, Claude, or similar)
- Send the draft to a native speaker to check tone, CTAs, and cultural nuances
- Native speaker makes edits and approves - 30-60 minutes of work instead of a full translation from scratch
- Ship it
Where to find native speakers for marketing post-editing: ProZ and TranslatorsCafe (filter for “marketing localization” + target language). For ongoing campaigns, having one or two trusted contacts per market as a permanent resource is worth it.
For translating high-stakes transactional emails (welcome, onboarding, win-back) where quality is critical, a service combining AI with human verification is an option - for example ChatsControl: upload a document or text, get a translation that’s gone through multiple review rounds. Works well for one-off jobs when you need quality above raw machine translation but aren’t ready to build a full TMS workflow.
As Omnisend notes on the AI + human approach:
Combining AI translation with human review is “up to 2x faster” than human-only, but human-only remains the gold standard for brand voice and high-stakes trigger emails like onboarding and win-back sequences.
Five brand failures that became case studies¶
These are real incidents cited across industry publications as textbook examples of what happens when localization gets treated as “just translation.”
KFC in China (1987). “Finger Lickin’ Good” was translated literally - the result: “Eat your fingers off.” The campaign had to be pulled. Classic literal idiom translation disaster.
Pepsi in Taiwan. “Come alive with the Pepsi Generation” → translated as “Pepsi brings your ancestors back from the dead.” Went out without native speaker review.
Amazon Sweden. Machine translation of product descriptions translated “rooster” to a Swedish slang word with an obscene meaning. Went live without human QA - classic MT-without-review failure.
Valentine’s Day in Brazil. Not one but dozens of brands every year send “Valentine’s Day” campaigns in February to Brazilian audiences, while the actual Dia dos Namorados on June 12 goes unmarked. Happens every year, at scale.
Gmail auto-translation bug. Emails with dynamic content (personalization, conditional blocks) can be misidentified by Gmail as being written in Hungarian, Norwegian, or Czech - and auto-translated directly inside the subscriber’s inbox. The result: garbled nonsense where your carefully crafted campaign was. Documented on Litmus Community. Fix: include <html lang="en"> attribute in your email code and a Content-Language header.
According to Smartlead.ai, 47% of consumers would stop buying from a brand after culturally insensitive messaging. Localization failures don’t just cost the campaign - they cost the customer relationship.
Localization checklist before every campaign launch¶
Save this for review before each language launch:
| Element | What to check |
|---|---|
| Subject line | Translated, natural, 36-50 characters in target language |
| Preheader | Translated (not left in English) |
| Tone and register | Matches market expectations (Sie/du, formal/informal) |
| CTA buttons | Rewritten by native speaker, not word-for-word translated |
| Holiday dates | Correct for target market (not copy-pasted from US version) |
| Date format | Adapted (MM/DD vs DD/MM, or written out in words) |
| Currency and prices | Converted to local, or both shown |
| Images | No embedded text, or localized versions exist |
| RTL (Arabic/Hebrew) | Template rebuilt, subject line correct |
| Push notification | Length checked after translation (iOS ~150, Android ~240) |
| Legal requirements | China: “AD” in subject; EU: GDPR opt-out; Canada: CASL |
FAQ¶
How much does it cost to localize an email campaign across 3 languages?¶
Depends on the approach. ESP-native localization (Klaviyo Smart Translations) is included in your plan - no additional cost. AI draft + native speaker post-edit: $20-50 per email depending on length and market. Full human translation + adaptation: $80-150 per email. For ongoing programs (5+ emails per month across 3+ languages), a TMS subscription ($100-500/month) typically pays for itself.
How do I prioritize languages on a limited budget?¶
Start with the languages of your largest markets by revenue or potential. Then markets where a competitor is already localized and pulling customers. Prioritize welcome series and abandoned cart first - highest ROI. For bulk newsletters, AI + light post-editing is sufficient.
Is automatic ESP translation good enough?¶
For basic transactional emails - often yes. For marketing campaigns where tone and CTAs matter - you need human review. ESP machine translation (like Klaviyo’s) is based on DeepL or similar - quality is good for standard content, but CTAs, idioms, and culture-specific phrases need a native speaker pass.
How do I measure the results of localization?¶
A/B test between localized and non-localized (English) versions for the same audience. Metrics: open rate, CTR, conversion rate, revenue per email. If your audience is too small for A/B, compare before/after performance on the same segment.
Is push notification localization more important than email localization?¶
Push is more critical in the context of immediacy: the notification is visible for 2-5 seconds, the tap decision happens instantly. Email gets more deliberate attention. But that’s exactly why push localization matters more - wrong tone or text truncated after translation means a lost tap with no recovery opportunity.
What if we don’t have native speakers on the team?¶
Three options: (1) ProZ or TranslatorsCafe - find a translator specializing in “marketing localization” for your target language; (2) Platforms with verified translator networks like Unbabel or Smartcat; (3) Local agencies - more expensive but appropriate for markets where brand voice is critical (Japan, China, Middle East).
Should we translate all emails or only the key ones?¶
Key emails first: welcome, abandoned cart, post-purchase, win-back. These have the highest ROI and the biggest impact on customer experience. For promotional newsletters, AI + light post-editing significantly reduces cost while maintaining acceptable quality.
Sources¶
- CSA Research “Can’t Read, Won’t Buy” B2C 2020 - survey of 8,709 consumers in 29 countries
- Smartlead.ai: Localizing Email Subject Lines - localized campaign statistics
- Crowdin: How to Localize Emails - tools and workflow guide
- Omnisend: Email Localization - market-specific practices and data
- SashiDo: Push Notification Character Limits - technical limits by platform
- CleverTap: Push Notification Character Limits - iOS and Android details
- Klaviyo Smart Translations - built-in localization documentation
- Remarkety: RTL Subject Lines - RTL support for Arabic and Hebrew
- Litmus Community: Gmail Mistranslation Bug - documented bug and fix