# Translation
Humanic doesn't just translate your emails it localizes them. When you're running campaigns across multiple languages or markets, Humanic adapts your message so it feels native to each audience, not like it was written in English and run through a converter.
***
### Translation vs. localization — what's the difference and why it matters
Translation changes the words. Localization changes the experience.
A translated email says the same thing in a different language. A localized email says the right thing for that audience in their language, with their cultural context, using the tone, formality level, and framing that actually lands.
When Humanic handles translation, it goes beyond converting text. It adapts tone for the market, adjusts formality levels where the culture demands it, rewrites idioms that don't carry across languages, and ensures the call to action feels natural rather than imported.
This distinction matters because a grammatically correct but culturally off email can feel cold, confusing, or even off-putting and that directly affects open rates, click-through rates, and trust.
***
### How translation works in Humanic
Translation in Humanic is prompt-driven, not menu-driven. You don't navigate to a translation settings panel and select languages from a dropdown. Instead, you describe what you need in your campaign prompt and Humanic handles the rest.
You can request translation as part of your initial prompt or as a follow-up instruction after generating your base email. Either approach works.
For example, after generating an English campaign, you might say: "Now create a Japanese version of this email for our Tokyo audience. Adjust the tone to be more formal and respectful, consistent with Japanese business communication standards."
Humanic will generate a localized version that reflects not just the language but the appropriate register and cultural sensibility for that market.
***
### What Humanic adapts when translating
**Language and grammar**
The core text is rewritten in the target language not word-for-word, but meaning-for-meaning. Humanic uses context from your campaign goal, your brand guidelines, and the email's structure to produce fluent, natural-sounding output.
**Tone and formality**
Different markets expect different levels of formality in commercial communication. Japanese audiences typically expect a more respectful, precise tone. German audiences often prefer directness and clarity. Brazilian audiences tend to respond well to warmth and energy. Humanic adjusts accordingly when you specify the target market.
**Idioms and expressions**
Phrases that work in English often don't translate. Humanic rewrites these rather than carrying them over literally so the meaning comes through even when the words change.
**Cultural framing**
The same offer can be positioned differently depending on the market. A discount framed as "limited time only" might work well in the US but land better as a premium exclusivity signal in other markets. Humanic can adapt the framing when you specify the cultural context you're targeting.
**Pricing and market context**
If your email references pricing, Humanic can adapt currency formats and regional pricing context when you provide the relevant details in your prompt.
***
### How to request a translation
You have two approaches depending on your workflow.
**Translate as part of the initial prompt**
Include the target language and audience in your first message. For example: "Create an onboarding email for new users, written in French for a French-speaking European audience. The tone should be professional but approachable."
Humanic will generate the email in French from the start, informed by your brand guidelines and the audience context you've provided.
**Translate after generating the base email**
Generate your email in English first, review it, and then ask for a translated version in a follow-up message. For example: "Translate this into Spanish for a Latin American audience. Adapt the tone to feel warmer and more conversational than the English version."
This approach works well when you want to establish the structure and messaging in English before adapting it for other markets.
***
### Tips for better translation output
**Always specify the market, not just the language**
Spanish for Spain and Spanish for Mexico are not the same. French for France and French for Canada differ in vocabulary, tone, and register. The more specific you are about the target market, the more accurate the localization.
**Describe the cultural tone you expect**
Don't assume Humanic knows the formality level you want. Say it explicitly "formal and respectful," "warm and casual," "direct and professional." This is especially important for markets where formality norms differ significantly from English-language defaults.
**Include brand voice context in your guidelines**
If your brand has a distinctive voice playful, authoritative, empathetic make sure it's captured in your Campaign Preferences brand instructions. Humanic carries this into translated versions so the voice stays consistent across languages.
**Review localized output with a native speaker for high-stakes sends**
Humanic produces high-quality localized content, but for campaigns going to large audiences or key markets, a quick review by a native speaker or in-country team member before sending is always a good practice. Catch anything that feels off before it reaches the inbox.
**Use iteration to refine**
Translation quality improves through conversation. If the tone in the first output feels slightly off, say so and describe what you're looking for. Humanic will refine the localized version the same way it would refine an English draft.
***
### Using translation with variation
Translation and variation work naturally together in Humanic. If you have multiple micro-cohorts within a single market for example, active users and inactive users in Japan you can generate cohort-specific variations and then localize each one.
The recommended workflow is to finalize your cohort variations in English first, then request localized versions of each. This keeps the review process manageable and ensures the core messaging is solid before localization adds another layer of adaptation.
***
### Frequently asked questions
**Which languages does Humanic support?**
Humanic can generate and localize email content in a wide range of languages. For best results, specify both the language and the target market in your prompt. If you're unsure whether a specific language is supported, test it with a short prompt before building a full campaign.
**Can I run the same campaign in multiple languages simultaneously?**
Yes. After generating your base email, you can request localized versions for each target market in sequence. Each version is generated independently within the conversation and can be refined separately before sending.
**Does translation affect deliverability?**
No. Deliverability is determined by your sending infrastructure, domain reputation, and email content quality not by the language of the email. Humanic manages domain reputation and deliverability practices across all campaigns regardless of language.
**What if the translated output uses the wrong level of formality?**
Correct it in the next message. Specify the issue clearly for example: "This sounds too casual for a Japanese business audience. Rewrite it with a more formal and respectful tone, appropriate for B2B communication in Japan." Humanic will adjust accordingly.
**Should I store translated versions separately in my knowledge base?**
If you regularly send campaigns to the same markets, uploading a short style guide or tone reference for each market to your knowledge base documents can help Humanic produce more consistent localized output over time without requiring you to re-specify preferences in every prompt.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://humanic.gitbook.io/humanic/advanced-features/hyper-personalization/translation.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.