Madison Logic has recently expanded on its capability to run a campaign in a language different than English.
Although some multi-language features were already present in the application (asset preview was available in 5 languages), you can now configure, set landing page, import and validate and deliver leads in one of the enabled languages we now fully support.
Supported Languages
The following language are all currently supported. If in the list you do not see the language you desire, please log in a ticket with the Product Department to request a new on.
Arabic
Bahasa Indonesian
Cantonese (traditional)
Dutch
French
German
Italian
Japanese
Korean
Mandarin (simplified)
Spanish
Sweden
Taiwanese
Thai
Turkish
Campaign Set Up
To configure a campaign in another language, you will need to start from the setting up the desired language in the Media Records tab:
Click on Edit on the right side of the screen, and choose your desired language from the Language drop down menu:
After picking the desired language from the drop down menu, you will see four different toggles: please choose the desired combination among the ones available:
Here is what the toggles mean:
Form Label: language in which the field name will be shown to the lead. This will also be the headers of the column of the Import Template given to the Partner via ML Partner.
Form Value: language in which information will be collected and uploaded for each lead.
Delivery Label: language in which the field name will be delivered to the client.
Delivery Value: language in which the lead information will be sent to the client.
Although you will probably mostly use one combination (i.e. all four options set on the non-English language), it is possible that a client would want to mix and match these options. Note that not all combinations are possible, specifically for the delivery labels and values, as they depend on the language configuration of the form fields and values language.
If a combination is not allowed, you will not be able to move the toggle and the toggle will be shown in a lighter blue color:
Once the options are chosen, click on the button SAVE and confirm the language in the modal:
IMPORTANT: if you already set up a campaign form field and then you change language, the existing fields you have configured will be removed. Please ensure you take note of your changes before you change from one language to another, in case you need to move from one language to another.
Note: The language configured in the Media Records will be the language in which policies on the landing page will be translated.
Form Fields Configuration
You are now ready to configure the form fields for the campaign. Click on the tab Form Fields:
The work email field is automatically translated in the language you have chosen, as this piece of information is mandatory and cannot be configured.
To add a standard field, simply select your choice from the drop down menu:
Once a standard field is added, the translation is automatically offered and will be shown under column Native Language Field:
To add a Custom Field click on the button Add Custom Question:
You will need to specify the type of custom field you are adding.
For option text, please write in either the English value or the Native language value as provided by the client. Before you are able to save, you will need to translate the value so both Native and English are present:
For option Multiple Choice:
Add the Field Name (either on the English left side or the Native language right side).
Use the central arrows to translate it.
Add the options either one by one, or by using the option ‘Comma separated’ , and click on the button Populate.
Once the option populate in the Multiple Choice Options section, click on the arrows to translate.
Once happy, click on DONE.
Option Check Box is the same as the Multiple Choice.
Option Decision is the same as the Text.
Important: Custom Fields can only be added on the line item level for multi-language campaigns, and not at the Opportunity level.
Landing Page
Once language and fields have been configured, ensure that the Landing Page details are also translated.
On the Asset tab, click on the edit icon under section Landing Page.
From here, please ensure buttons and and policies are in the right.
Note: the Download header and the Thank you Notes are not automatically translated, but you can manually translate it, if necessary. Please ensure to have the translation ready, then you can copy and paste it in the apposite places.
Once these checks are performed, you can continue setting up the rest of the campaign, and set it live.
How Multi-Language Campaigns Appears in ML Partner
The language identifier for each campaign is shown directly on the Reservation Card, so Partner can easily identify that the campaign is not in English:
Note: the language identifier is always present, even for campaigns run in English.
Clicking on the Details button on the reservation card also shows a mapping between the English fields and the non-English fields:
We also ensured all Partners have the campaign details in the file they export that contains the campaign details.
If they reserve a non-English campaign, upon clicking the button EXPORT in the Reservation tab they will see a spreadsheet that has the word ‘native’ in the name: that is the one containing the information of the non-English campaign:
Note: For non-English campaigns, ML Partner Import tab will reject any lead that is not in the specified language. This is done via an enhanced language detection on the import file data.
How are leads validated on non-English campaigns?
Madison Logic does not currently tap into non-English databases, but it does rely on its powerful database and lead quality checks available in English.
This can be achieved via a strategy called ‘reverse mapping’:
Reverse Mapping: the Lead Validation platform will detect if a lead is being uploaded for a non-English campaign, and will use the English value stored in ML Console and use that English value through the validation process.
If the lead is found valid, then it will substitute the English value with the original imported value, and send the lead out for delivery.
In a nutshell, there are two reverse mapping that happen when a lead is uploaded on non-English campaigns:
LVP reverses the lead to the English value stored in ML Console Form Fields tab, and use it to validate the information in English.
LVP reverses the lead from English to the original imported value before the lead is sent out to for delivery.
For this reason, it is extremely important to ensure that all campaigns run in a non-English language have their corresponding English translation stored into ML Console. Without the English values, the Lead Validation Platform will not be able to validate and perform quality checks on leads.
Note: remember, the Lead Validation Platform also includes manual QA, if the automatic process is not sufficient to deem the lead valid or invalid. Manual QA is thus performed in English.