Google Tag Manager

Forum Discussion

emily_wri's avatar
emily_wri
Supporter
20 days ago

Handling Translations

Hi - I'm wondering how people have found success in structuring their teams and workflows to cater to different languages? We are an English-first app, but have it available in Spanish, French and German.

So far, I've just completely excluded the additional languages from campaigns because we don't have the bandwidth to handle other languages right now. We are a small team of English speakers (I took French immersion in school but wouldn't rely on it since I haven't used it in a long time). 

I have a few different use cases which could probably benefit from their own approach:

  • One-off campaigns: regular monthly newsletters, feature releases, surveys etc. 
  • Canvases: Welcome series, purchase conversion, churn reduction canvases: these are fairly complicated canvases which are updated once per month, maybe. We typically are testing timing, subject lines, copy etc., so we are changing them. 

I want to reduce the manual workload as much as possible, so the trade-off of individual language analytics vs. having to keep multiple canvases updated is a pretty big consideration. 

Curious what solutions other people have landed on. What's your current workflow? How did you land on it? Did you try something prior that didn't work? Are you using separate canvases, user journeys or simply just calling liquid within the message? Are you using any of the Braze language tools? Are you using spreadsheets or any tools like Phrase or Lokalise? Any drawbacks to your current set up?

Thank you, I appreciate any help you're all willing to give!

3 Replies

  • Hi emily_wri​

    First of all, you are absolutely not alone here. Localization/Translation is a massive project, and we've even seen dedicated TEAMS for localization in some of our clients' companies.

    One of our clients uses Lokalise, but even then, we are currently going through a massive project where we are adding four more languages to existing  ~100 campaigns/canvases that  currently have three languages. We are using the Braze {% translation %} tags for this. 

    We've built some custom scripts to scrape every single campaign/canvas with a translation, and we're doing a lot of file matching work. It's not pretty and straightforward, but it's the most streamlined way we've come up with so far. This way we can add the four new languages to each of the files and re-upload each of the files to the existing Braze campaign/canvases.

    Happy to chat more about this! Please feel free to reach out at allan.heo@fornowmarketing.com

    Best,

  • kriziac's avatar
    kriziac
    Collaborator

    Hi there. We're a language learning app and we send all comms localised to multiple languages. To do this, we use Phrase and Liquid. If we're trying to isolate or target specific languages, we do this through Canvases and/or setting up the Segments beforehand.

    We use Phrase because (I believe) it came first, and it's used to localise the app for many languages. Braze came later, and so any and all localised content for both the app and for CRM just go through Phrase.

    Happy to go into more detail and answer what I can if you drop me a message. There may be some things I won't be able to answer because I've inherited the setup that I am currently working on optimising, but if I can answer, I will.

  • Hi, 

    I recently added a post to me Linked In on this. 

    Would be more than happy to go through the two providers I have experience with if that helps. 

    But it's super simple. 

    Alternatives to TMS would be Gsheets (sheetdb/sheets.io style if low send rate limits are ok) or Catalogs (probably not the best) or standard liquid with fixed masters each month.