/localize-campaign

name: localize-campaign
description: "Localize campaigns for multiple markets. Use when: translating assets, adapting references, adjusting compliance."
argument-hint: "[target-markets]"

/digital-marketing-pro:localize-campaign

Purpose

Full campaign localization across multiple target markets. This command takes all campaign assets — emails, ads, social posts, landing pages, video scripts, push notifications — and adapts them for each target market. It goes far beyond translation: cultural references are adjusted, compliance elements are modified per region, SEO is localized, creative recommendations are adapted, and assets are prepared for multilingual publishing.

This is the comprehensive localization workflow for market expansion. Where `/digital-marketing-pro:translate-content` handles a single piece of content, `/digital-marketing-pro:localize-campaign` orchestrates the localization of an entire campaign across multiple markets simultaneously. It coordinates translation service routing per language, transcreation for emotional content, market-specific compliance additions, cultural adaptation based on Hofstede cultural dimensions, localized SEO, RTL formatting for applicable languages, and produces a deployment-ready package per market with quality scores and publishing checklists.

Input Required

The user must provide (or will be prompted for):

• **Campaign assets**: Content for localization, provided as:
• File paths per asset type (e.g., "emails: /campaign/email-welcome.html, /campaign/email-follow-up.html; ads: /campaign/fb-ad.txt, /campaign/google-ad.txt; social: /campaign/ig-post.txt")
• A campaign directory (e.g., "/campaign-q1/") — all files will be categorized by type based on naming conventions or metadata
• Inline content blocks with asset type labels
• **Target markets**: One or more market codes in language-region format (e.g., hi-IN, de-DE, ja-JP, fr-FR, ar-SA, pt-BR, es-MX). Each code specifies both the language and the cultural/regulatory context
• **Campaign brief or strategy document**: Optional — provides campaign objectives, messaging hierarchy, key themes, and audience segments. Used to inform transcreation decisions and ensure localized versions maintain strategic alignment
• **Market-specific compliance requirements**: Optional — additional regulatory, legal, or industry requirements per market beyond what is already in the brand profile (e.g., "Germany requires Impressum link", "India requires MRP display", "Saudi Arabia prohibits alcohol imagery references")
• **Budget allocation per market**: Optional — if provided, influences prioritization (higher-budget markets get full transcreation and deeper cultural adaptation; lower-budget markets get quality translation with standard adaptation)
• **Priority markets**: Optional — markets to process first and with the most thorough adaptation. Other markets receive standard localization
• **Asset priority**: Optional — which asset types are most important (e.g., "landing pages are highest priority, social posts are secondary"). Affects depth of review and transcreation effort

Process

1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Extract full language configuration — `do_not_translate` terms, `translation_preferences`, `locale_formatting` rules per market, approved markets list. Load compliance rules for every target market from `skills/context-engine/compliance-rules.md`. Check for guidelines at `~/.claude-marketing/brands/{slug}/guidelines/_manifest.json` — if present, load voice-and-tone rules, messaging hierarchy, channel style guides, and any market-specific brand guidelines. Check for custom templates at `~/.claude-marketing/brands/{slug}/templates/` — localized templates may already exist for some markets. Check for agency SOPs at `~/.claude-marketing/sops/`. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults. 2. **Inventory all campaign assets**: Enumerate every asset from the provided sources. Categorize each by type (email, ad, social post, landing page, video script, push notification, SMS, blog post). For each asset, analyze the content to classify it as:

• **Factual/informational**: Product descriptions, specifications, terms, pricing — suitable for direct translation
• **Emotional/creative**: Headlines, CTAs, slogans, hero copy, storytelling — requires transcreation
• **Compliance-sensitive**: Disclaimers, consent language, legal text, privacy notices — requires market-specific adaptation
• **SEO-dependent**: Landing pages, blog posts, meta content — requires localized keyword research

Report the full inventory to the user: total asset count, breakdown by type, breakdown by content classification, and estimated processing scope per market. 3. **For each target market**, execute the following localization pipeline: a. **Route translation service**: Run `python "${CLAUDE_PLUGIN_ROOT}/scripts/language-router.py" --action route --source "{source_lang}" --target "{market_lang}"` to select the optimal translation service for this language pair. Log the selected service. b. **Translate factual content**: Process all factual/informational assets through the routed translation service via the appropriate MCP server (deepl, sarvam-ai, google-cloud-translation, or lara-translate). Pass do-not-translate terms, glossary entries, formality settings, and formatting preservation flags. Score each translation via `python "${CLAUDE_PLUGIN_ROOT}/scripts/language-router.py" --action score`. c. **Transcreate emotional content**: For all emotional/creative assets, apply the transcreation methodology from `skills/context-engine/transcreation-framework.md`. Produce 2-3 creative adaptation options per piece, each with:

• The adapted content in the target language
• Back-translation for