Marketo form embedded on website

Forum|Forum|1 day ago
August 12, 2026
6 replies
57 views

Hi,

We need some guidance on handling non-English job titles in Marketo.

We have a non-English landing page with an embedded Marketo form, and the form labels/input fields will also be in the local language. Currently, we have automation that derives Job Function and Job Level from the Job Title field when the title is entered in English.

The challenge is that visitors on these localized pages may enter their job titles in non-English languages (for example, Chinese, Japanese, Spanish, German, etc.). Since our existing mapping logic only recognizes English job titles, these records are expected to default to "Other" for both Job Function and Job Level.

Could you please advise on recommended approaches for handling this scenario?

Thanks,

Deepthi.

SanfordWhiteman

Level 10

Well, seems you have 2 options:

Auto-translate the Job Title into English, store the result in a custom field Job Title EN (translated), then use your existing mapping logic against the new field.
Keep the Job Title in its original form and add new mappings that more carefully (and accurately) take locale into account.

For 1. you can call Bing/Google/etc. cloud translation services using a webhook.

(Far as I’m aware, there’s no officially supported, cross-browser way to consume these services in client JS. Chrome desktop and Edge now have a built-in, non-cloud translation API but other browsers don’t. There’s an unsupported Google Cloud Translate API endpoint that has basic results, but I feel it won’t be industry-appropriate - could be wrong, give it a try! There are other translation services designed for the browser side but I couldn’t personally vouch for ‘em.)

PeeyushSachdeva

Level 4

@DeepthiGo1,

I think the current approach of deriving Job Function and Job Level based on a predefined set of Job Title mappings can become difficult to maintain as the number of titles and languages increases. Every new or previously unrecognized title would require additional mapping, and this becomes especially challenging when titles are submitted in non-English languages.

One approach I would suggest is exploring an AI-based skill/flow that can interpret the Job Title regardless of the language and then map it to your predefined Job Function and Job Level values. This would reduce the dependency on maintaining an ever-growing list of individual job-title mappings and could also provide better coverage for new or unexpected titles.

You could still keep the AI output constrained to your existing Job Function/Job Level taxonomy to ensure consistency.

Hope this helps!

D

DeepthiGo1Author

Level 2

Thank you @PeeyushSachdeva…

Any recommendation you have for AI tool ?.

PeeyushSachdeva

Level 4

@DeepthiGo1 ,

I would recommend exploring an LLM-based solution such as OpenAI/Claude, especially if your organization already has access to it. The use case would be to pass the Job Title to the AI, have it interpret the title regardless of the language, and then classify it into our predefined Job Function and Job Level values.

If your organization already has an approved AI platform, I’d suggest checking that option first before introducing a new tool.

Michael_Florin-2

Level 10

Is that free-text form field for Job Title even valuable for you or do people enter all sorts of things? Could it be a select field?

And another thought: Why don’t you bring Job Function and Job Level directly on your forms and remove Job Title? And make them select fields, of course. Then you can easily maintain a local language version that’s visible for your users and save the English values in the database.

PeeyushSachdeva

Level 4

Hey @Michael_Florin-2 , My understanding is that adding Job Function and Job Level as extra fields on the form isn't ideal, the more fields you ask for, the more it tends to lower completion rates. Could be wrong though, curious if that's held true in your experience.

Sign up

Login with SSO

Login to the community

Login with SSO