strategist-translations

To audit Braze campaign translations, compare source strings against localized translation maps to identify missing locales and stale content. This process surfaces locale gaps across campaigns, canvases, email templates, and content blocks before launch.

Update Braze canvas and email template translation maps by preparing localized strings and submitting them via Braze REST translation endpoints. You must handle draft-state constraints for live canvases and ensure appropriate permissions before pushing updates.

Managing Braze translations requires campaigns.translations.get/put, templates.translations.get/update, canvas.translations.get/update, and content_blocks.translations.get/update REST API permissions. Some endpoints may have early access or beta status constraints.

You can preview translated message variants in Braze after submitting translation_map updates by verifying propagation through the translation endpoints. This confirms localized content renders correctly before campaign launch across all target locales.

Braze canvas translation updates may not apply to live versions due to draft-state constraints. Live canvases require translations to be handled through draft modifications before changes can propagate to the active canvas flow.

This translation management approach integrates with external localization workflows and TMS platforms by preparing translation maps for orchestration. It synchronizes locale variants across Braze campaigns, canvases, templates, and content blocks to prevent source drift.