marketer-localize-campaign

Localize campaign

Take one finished campaign and adapt it to N markets — translated copy, culturally appropriate visuals, right-to-left handling for AR/HE, and text-expansion-safe layouts. Built for consistency (same campaign identity per market) and speed (one batch per locale).

When to Use

• User has a shipped campaign in one market and needs to launch across 3+ additional locales.
• "Localize across DE, FR, JP, BR, ES" / "translate + adapt creatives per market" / "RTL version for AR".
• Master campaign has on-image text, people, or cultural motifs that need swapping per locale.
• Do NOT use for pure text translation (use an LLM directly) or for a fresh campaign (use marketer-campaign-kit first, then this skill).

Prerequisites

Ask up front if the brief doesn't cover it (combine into one message):

1. Master campaign assets — paths/URLs to the approved creative. What's already finalized (hero, ad variants, email, LP)?
2. Target locales — language + region (e.g. de-DE, fr-FR, ja-JP, ar-SA, pt-BR). Region matters for cultural appropriateness.
3. Translated copy — is it done? If yes, paste it. If no, note which copywriter/vendor owns it (don't auto-translate ad copy — compliance risk).
4. Cultural swaps needed — people (face/ethnicity), settings (interior style, streetscape), props (food, gestures)? If the hero has a specific person, does that persist or get replaced per locale?
5. RTL locales in scope — Arabic, Hebrew, Farsi? Layout needs to mirror, text extends right-to-left.
6. Deliverable naming — ad-platform uploaders expect {campaign}_{locale}_{size}.webp.

Never auto-translate ad copy without a reviewer — legal/compliance owns sign-off.

How to Run

1. Inventory the master assets. List every creative that needs localizing (hero, 6 ad variants, email, LP hero = 9 per locale × 5 locales = 45 assets).
2. Collect translated copy per locale BEFORE generating. Don't batch-run with English placeholders — you'll re-render everything.
3. Choose adaptation strategy per asset:
   • Text-only change (headline on a clean bg): use ideogram-v3 with the translated copy and same visual.
   • In-place motif swap (person, setting): use an edit model (qwen-image-edit-plus, flux-kontext-pro) with the original image + a locale-specific prompt.
   • Full regeneration (complex cultural swap): generate fresh from the original prompt + locale guidance, referencing the original as image for composition.
4. Write per-locale manifests. One manifest per locale keeps naming clean and lets you parallelize across locales without collision.
5. Estimate per locale.

   gen-ai batch run localize-de.json --dry-run
   

6. Run locales in sequence, not in parallel. Review one locale's output end-to-end before kicking off the next — catching a cultural mismatch in DE means fixing the prompt before JP, FR, and BR inherit it.

   gen-ai batch run localize-de.json -c 4 -o ./out/de-DE
   

7. Review with a native speaker per locale. Every locale. No exceptions. Especially for JP (text rendering), AR (RTL + text), and any market with a dedicated country manager.
8. Package and hand off. Folder per locale, filename includes locale code, results.json archived for audit.