engineer-localization

What problem does it solve?

Engineers and platform integrators often struggle to reliably connect Braze with translation management systems, manage authentication differences, and keep localized content synchronized without overwriting production assets or mismatching locale codes. This skill reduces integration drift by documenting pipeline patterns, authentication methods, webhook orchestration, content format expectations, and staging best practices.

Core Features & Use Cases

• Integration Blueprints: Clear, scan-friendly setup steps for Transifex, Smartling, Phrase, Lokalise, LILT, Crowdin, and Tangerine including required API endpoints and mapping guidance.
• Auth & Pipeline Patterns: Quick reference for bearer tokens, OAuth client credentials, basic auth, and the distinction between Push-Pull exports and Connected Content at-send-time calls.
• Operational Guidance: Recommendations for webhooks vs polling, locale normalization to BCP 47, staging translated templates in separate workspaces, and avoiding credential leakage in message bodies.
• Use Case: Configure a Transifex Push-Pull workflow to export campaign strings from Braze, trigger translations, and reimport localized templates into a QA workspace before production rollout.

Quick Start

Create a step-by-step implementation plan to export Braze message strings, map locale keys, and configure authentication and webhooks to implement a Push-Pull integration with a translation management system.