Prepare translated email copy in Migma as a connected set: subject line, preview text, opening, and main action. Before sending through Klaviyo, review that set in the actual destination version. A translated body does not establish that the inbox still introduces it accurately.
The subject and preview have different jobs. The subject identifies the message or creates a relevant reason to open it. The preview can add the detail that helps the reader decide. Translating those lines separately can create repetition, a missing qualification, or a promise the body no longer supports.
Klaviyo’s subject-line article discusses using preview text to complement the subject. The process here applies that idea to a narrow localization review, with original examples and a specific custom HTML handoff check.
Write the message’s fixed meaning first
Record the facts that every language version must preserve: what is available, who it is for, the action, and any relevant timing or eligibility condition. Also record which words may change naturally for the local audience.
For an original example, imagine an opted-in workshop invitation. The approved meaning is that registration is open for a workshop aimed at people new to the product. There is no approved discount and no evidence that places are nearly full. Every translation should preserve that boundary even if a more urgent phrase sounds appealing.
Give Migma this meaning brief with reviewed brand guidance. Ask for natural local-language copy and an explanation of any wording that could change the offer. Have a qualified language reviewer check meaning and tone. A fluent-looking sentence is not enough evidence on its own.
Review the pair before reading the whole email
Place the subject and preview beside each other. Read them as the recipient would, without relying on the image or opening paragraph to repair ambiguity. If both say “Registration is open,” use the preview for useful context rather than repeating the announcement.
An English planning pair might say “Your first workspace workshop” and “See the agenda and choose a session.” Those lines are an illustrative brief, not a tested performance claim. A local version may use a different sentence structure while preserving the same workshop and action.
Do not put a material condition only at the end of a long preview. Inbox space varies. The official Klaviyo preview-text guide explains that devices and clients show different amounts. Review the shortest visible portion for clarity, rather than assuming one character limit works everywhere.
Check these four forms of drift
| Drift | What a reviewer sees | What to resolve |
|---|---|---|
| Repetition | Subject and preview repeat the same announcement | Add relevant detail without a new promise |
| Stronger claim | Translation introduces scarcity or a guarantee | Restore the approved meaning |
| Missing context | The workshop sounds suitable for everyone | Preserve the intended audience |
| Destination mismatch | Inbox invites registration but button opens a general page | Align the action and actual destination |
Keep the language reviewer’s decisions with the final copy. If a phrase has more than one plausible meaning, resolve that question before the email enters the sending workflow.
Respect the destination template type
Klaviyo’s current preview-text documentation makes an important distinction: its Preview Text input feature is supported in drag-and-drop templates. For custom HTML, including custom HTML with drag-and-drop support, the email designer should insert the desired preview text into the beginning of the email code. Text-only email uses the beginning of its content.
That means a field visible in one workflow is not evidence that every exported HTML template uses it the same way. Ask the destination owner to identify the actual template type and verify the populated message. Do not paste a hidden-preview snippet blindly or assume a source preview overrides the destination.
Migma’s export guidance supports selecting a language for export and downloading separate language HTML files. Keep those files and their approved inbox copy clearly matched. Review the chosen export route’s current constraints before using it for a translated email.
Inspect what the inbox actually shows
Use an authorized test from the final sending platform. Check the sender name, subject, displayed preview, opening, and action in the same message. If the preview unexpectedly contains navigation text or image alt text, inspect how preview text is implemented rather than simply shortening the subject again.
Review a narrow inbox as well as desktop when available. Look for the point at which the subject loses context, awkward line breaks, and punctuation that changes the meaning. Use a real language reader for right-to-left or unfamiliar-script review instead of relying only on a screenshot’s visual balance.
Keep the essential promise understandable if the client shows little preview text. This is an editorial design goal, not a guarantee that every inbox will display the same words or length.
Approve one connected language version
Store the final subject, preview, body reference, language, destination template, and reviewer together. If the English offer later changes, identify the affected language versions and review them again. Do not assume that editing one source automatically updates every destination copy.
Start with one language version and one real inbox test. Once its meaning and implementation are correct, repeat the same review for each remaining language. The useful deliverable is a coherent message the recipient can understand, with evidence that its actual inbox introduction matches the email they open.
Frequently asked questions
Does translated body content prove the subject is translated correctly?
No. Review the subject, preview, opening, and action as one connected promise, with a qualified language reviewer where needed.
Where does Klaviyo preview text belong for custom HTML?
The official guide says the designer should insert it at the beginning of the email code. The Preview Text input feature is supported in drag-and-drop templates; verify the actual template type.
Should I use one fixed preview-text length for every language?
No. Wording and displayed space vary by language, device, and client. Keep the essential meaning early and inspect the actual inbox result.
Does changing the Migma source update every exported language template?
Do not assume that. Identify each affected destination version, apply the approved change through its supported workflow, and verify the result.