Lead quality by language: cost per interview in multilingual ads

What it does

Multilingual campaigns hide a trap. Lead volume per language is easy to see, but languages differ in what happens next. One language may bring many cheap taps from people who do not meet a job's basic requirements, while another brings fewer leads that almost all reach an interview. If you allocate budget by cost per lead, you can end up feeding the language that looks efficient and starving the one that actually fills positions. The only fair comparison is cost per interview and cost per hire for each language over the same period.

Track two different languages. The first is the language of the ad and the landing page, which is what you targeted and paid for. The second is the language the person actually speaks with your recruiter. They often differ: a Russian speaker may click an English ad, and a Spanish page may attract bilingual candidates who prefer English. Record the page language automatically, for example from a lang parameter in the landing page address, and have whoever answers the lead record the candidate's language at first contact. Comparing the two shows whether targeting reaches the people you intended.

Structure the account so spend separates cleanly. Give each language its own campaign or ad set, its own ad copy and a landing page version selected by a parameter such as ?lang=ru, and make the language visible in the UTM tags. Remember that search volume depends on the words people type and on the location, not on the campaign's language setting. In a live check in October 2026, truck-driver keywords in the US had Latin-script searches in the thousands per month and Cyrillic searches in the tens. Plan budgets per language from real demand, not from the size of the community.

AdAce Ads keeps both languages with each lead. The tracking script stores the page address and page language, and the lead message in the client's Telegram topic has buttons for the candidate's language next to the status buttons. The service then shows cost per interview and cost per hire by candidate language as well as by campaign. Other tools help with the setup: changing an ad's final URL with a one-click language parameter (lang=ru, uk, en or es), the Meta multi-language campaign with one ad set per language, and the demand estimate in “Analytics” → “Demand”, which splits monthly searches into Latin-script and Cyrillic keywords.

Read the results carefully. The language with the lowest cost per interview may also have a hard ceiling on volume, so doubling its budget will not double interviews. Small numbers swing a lot, so compare over weeks rather than days and look at the share of leads that reach an interview as well as the cost. When a language underperforms, check the basics before cutting it: does the ad copy sound natural, does the landing page open in the same language, and do recruiters who speak it answer quickly? Often the fix is in the funnel, not the budget.

Why it helps

• Each language is judged by interviews and hires, not by lead volume.
• Both the page language and the candidate's real language are recorded.
• Results by language guide budget and ad copy decisions.
• Demand checks show realistic search volume per script before launch.

How to set it up

1. Give each language its own campaign or ad set and a landing page version with a lang parameter.
2. Install the lead tracking script from “Analytics” → “Leads” on every language version of the site.
3. Ask recruiters to set the candidate's language under each lead in the Telegram topic.
4. Mark a status for every lead: wrote, interview, hired or not a fit.
5. After a few weeks, compare cost per interview and per hire by candidate language in AdAce Ads.
6. Check “Analytics” → “Demand” before adding budget to a language.

Good to know