Forms in Other Languages

[Joseph_Moran2]

We are in the process of launching a new website. As we were reviewing our old forms, we began looking into how we would handle translations. Having 7 versions of the same form (Contact Us English, Contact Us French, Contact Us German, etc.) sounds aweful to us. I am curious, how have others handled translations of forms in Marketo?

Sanford Whiteman shared this wonderful method for handling translations, https://blog.teknkl.com/smoothing-embedded-marketo-form-loads/. Has anyone tried this approach? Any challenges we should anticipate?

Champion Program

[Joseph_Moran2]

Do you store the translations in the token then or within a language dictionary on the site?

[SanfordWhiteman]

If I don't have any (non-Marketo) place to host cross-domain JSON then I'd put everything in a token, yes.

[Joseph_Moran2]

Can you elaborate on what cross-domain JSON would be? I am guessing you would use this for translating all forms then, correct?

[SanfordWhiteman]

Can you elaborate on what cross-domain JSON would be? I am guessing you would use this for translating all forms then, correct?

I was alluding to the fact that in order to store your language dictionaries as standalone .json file(s) those files would have to be hosted...

• in Marketo as a Design Studio asset, only for forms on Marketo LPs; or
• on a 3rd-party site, only for forms embedded on that site; or
• on a webserver that allows cross-domain fetches -- that is to say, not on a webserver that was left at typical defaults -- for either of the above cases

I admit my phrasing up there was pretty weird.

[Grégoire_Miche2]

Please move this to Products​. Champion Program​ is for questions about the program itself.

-Greg