ThisCalculator

Everyday

Google Ads AI Campaign Localization Beta: Languages & Limits

Updated · Standard formula, shown below

Google Ads AI campaign localization beta supports a specific set of languages and has defined workflow limits. This article explains which languages are currently supported, how the localization workflow operates, and the key constraints you need to know before using it.

Background: What Is the AI Campaign Localization Beta?

Google Ads has been testing a feature that automatically translates and adapts your campaign assets (headlines, descriptions, images, and even final URLs) into multiple languages. The goal is to let advertisers run a single campaign that serves ads in several languages without manually creating separate campaigns per language. This is part of Google’s broader push toward AI-driven campaign management, similar to Performance Max but applied specifically to language targeting.

The beta is not available to all advertisers. It is typically rolled out to select accounts that meet certain spending and policy requirements. Google has not published a full public documentation page, so most details come from advertiser reports and Google support threads.

Supported Languages in the Beta

As of the latest available information, the beta supports a limited set of languages. Based on advertiser reports and Google’s own help center updates, the following languages are commonly included:

  • English (all major variants: US, UK, AU, CA)
  • Spanish (Spain and Latin American variants)
  • French (France and Canadian French)
  • German
  • Italian
  • Portuguese (Portugal and Brazilian)
  • Dutch
  • Polish
  • Swedish
  • Japanese
  • Korean
  • Chinese (Simplified and Traditional)

Notably absent are languages like Arabic, Hindi, Russian, and Turkish, which are common in global advertising. Google may expand the list over time, but as of now, these are the languages advertisers have confirmed working in the beta.

How the Localization Workflow Works

The workflow is designed to be mostly automated, but it requires a few manual steps from the advertiser. Here is the typical process:

  1. Create a campaign with a primary language (e.g., English).
  2. Enable localization in campaign settings (only visible if your account is in the beta).
  3. Select target languages from the supported list.
  4. Upload your assets (headlines, descriptions, images, and optionally a final URL suffix).
  5. Review auto-generated translations in the asset preview pane.
  6. Publish the campaign. Google then serves the localized version to users searching in those languages.

The translation is not a simple word-for-word swap. Google uses its machine translation models, then applies ad-specific adjustments (e.g., keeping keywords in the headline, preserving brand names, and adapting call-to-action phrases to local conventions). You cannot manually edit the translated assets before publishing—you can only approve or reject the entire set.

Key Limits and Constraints

The beta has several hard limits that advertisers often overlook:

  • Asset count limit: You can only localize up to 5 headlines and 3 descriptions per ad group. If you have more, the extra ones are ignored.
  • Character limits: Translated assets must still respect Google’s standard character limits (30 for headlines, 90 for descriptions). If a translation exceeds this, Google truncates it, which can break the message.
  • No manual override: You cannot edit the translated text. You can only approve or reject the whole batch. If you need a specific wording, you must create a separate campaign in that language.
  • Final URL localization: If you want to send users to a localized landing page, you must provide a URL suffix like ?lang=fr or use a redirect. Google does not automatically rewrite your final URL.
  • Budget and targeting: The localized campaign uses the same budget and targeting as the original. You cannot set different bids per language.
  • Reporting: Performance data is aggregated across all languages. You cannot see separate metrics for each language within the same campaign.

Common Problems and How to Avoid Them

Advertisers in the beta report a few recurring issues:

  • Translations that sound unnatural: Machine translation is not perfect. For example, a headline like “Get 50% Off Today” might translate to something that sounds too aggressive in Japanese. Always review the preview carefully.
  • Truncated text: German and Polish translations often run longer than the character limit. Google will cut them off, which can ruin the message. Check the preview for truncation warnings.
  • Images not localized: The beta only translates text. If your images contain text (e.g., a banner with a promo code), it will not be translated. You need to upload separate images per language manually.
  • Mismatched keywords: If your keywords are in English only, the localized ads may still show for English queries, not for localized ones. You need to add localized keywords manually or use broad match with smart bidding.

Comparison: Localization Beta vs. Separate Campaigns

Many advertisers wonder if the beta is worth using instead of creating separate campaigns per language. Here is a quick comparison:

  • Setup time: The beta is much faster—one campaign instead of five.
  • Control: Separate campaigns give you full control over translations, bids, and landing pages. The beta gives you none of that.
  • Performance data: Separate campaigns let you see which language performs best. The beta hides that data.
  • Budget allocation: With separate campaigns, you can allocate more budget to high-ROI languages. The beta uses one shared budget.

In practice, the beta is best for advertisers who want to test new markets quickly without a big setup investment. If you are scaling a proven product internationally, separate campaigns are usually the better choice.

Costs and Billing

The localization feature itself is free—you only pay for clicks and impressions as usual. There is no extra fee for the translation or the AI processing. However, be aware that your ads may now show in more auctions, which can increase your overall spend if you don’t set a strict budget. Also, since the campaign targets multiple languages, your click-through rate might initially drop as the AI learns which translations perform best.

Frequently Asked Questions

Can I use my own translated assets in the beta?

No. The beta only uses Google’s auto-translations. You cannot upload your own translations for the same ad group. If you need custom translations, you must create a separate campaign in that language.

Does the beta work with Performance Max campaigns?

No, the localization beta is currently only available for Search campaigns. Performance Max has its own language targeting options, but it does not include this specific localization feature.

What happens if my keywords are in English but my ads are in French?

Your ads will show for French searches that match your English keywords if the search intent is similar. Google uses its language understanding to match queries, but it is not perfect. You may see lower relevance scores initially. It is recommended to add localized keywords to your ad group.

Can I exclude certain countries from the localized campaign?

Yes, you can still set geo-targeting at the campaign level. The localization only affects the language of the ads, not the geographic targeting. You can target only France and Canada, for example, even if you have French as a target language.

How long does it take for the localization to go live?

Once you publish, the localized ads typically go live within a few hours. However, the AI may take several days to optimize which translation variant to show for each query. You should wait at least a week before judging performance.

Is the beta available in all Google Ads accounts?

No. It is invite-only. You can request access through your Google Ads representative, but approval is not guaranteed. Google typically prioritizes accounts with a history of international advertising and high spending.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.