How to make ad creative faster, especially across languages

This page may contain affiliate links from which Blur Studio earns commissions.

Ad creative that works slows down fast once you need variations, and it slows down more once you need those variations in other languages. Most of that slowdown isn't the creative idea itself, it's the mechanical work of adapting it: rewriting copy, re-recording voiceover, re-rendering video for each market, then uploading everything back into whichever ad platform you're running. ElevenLabs built a tool specifically to collapse that mechanical step.

What does Ads Engine actually automate?

Ads Engine connects directly to your existing ad accounts on Google Ads, Meta Ads Manager and LinkedIn Campaign Manager through their own APIs, pulls your active creative straight from the account, and localizes the text, images and video across more than 50 languages. The video localization specifically uses ElevenLabs' Dubbing v2, which preserves the original speaker's voice characteristics and emotional delivery across languages rather than swapping in a generic different-sounding voice, which matters for keeping a consistent brand voice as you expand into new markets. Once localization is done, the finished ads push back to the platform they came from, so you're not manually re-uploading everything.

The workflow detail worth knowing: you can configure a localization pipeline once and save it as a reusable template, then apply that same pipeline to future campaigns automatically. That's the actual speed gain here, not the first localization, which still takes setup time, but every campaign after the first one.

A worked comparison: localizing one 30-second video ad into 5 languages the traditional way (a translator per language, a voice-over artist or re-recording session per language, a video editor re-rendering each version, then someone manually uploading 5 separate creatives into 5 campaign variants) typically takes several days of coordinated work across multiple people, even when everyone responds quickly. With Ads Engine, once your pipeline is configured, the same 5-language localization runs as a single job, with the native-speaker review being the only step that still genuinely needs a human and can often happen the same day. The first campaign you localize this way won't feel dramatically faster, since you're building the pipeline at the same time; the second, third and every campaign after that is where the time saved compounds, since you're reusing a setup instead of rebuilding the whole process from scratch. If you dub outside Ads Engine, tools are compared in best AI dubbing tools for training and product videos.

What I'd actually tell you before you set this up

Ads Engine is built to speed up localization and iteration on creative you already have, not to invent a new campaign concept from a blank page. If your actual problem is "we don't have a good ad idea yet," this tool doesn't solve that; it solves "we have a good ad idea and need it in nine languages by Friday." Be clear about which problem you actually have before you set this up, because the tool's real value only shows up on the second half of that sentence. A rough rule of thumb: if you're spending more time on the ninth version of an already-approved ad than you spent coming up with the idea in the first place, Ads Engine is solving your actual problem; if you're still iterating on whether the idea itself works, it isn't yet, and no amount of fast localization fixes a concept that hasn't found its message.

The other thing worth testing before you trust it with a real campaign: review every localized version against a native speaker's judgment, not just the automated output. Voice-preserving dubbing and automated translation have both gotten genuinely good, but "good" and "sounds natural to someone who actually speaks the language" aren't automatically the same thing, especially for anything idiomatic or market-specific in the copy.

Step by step: speeding up ad creative with Ads Engine

1. Start with one ad that's already proven to work in your home market; localization is faster and safer to test on something validated than on something brand new.
2. Connect your Google, Meta or LinkedIn ad account and pull that creative into Ads Engine.
3. Set up the localization pipeline for your target languages, including the voice-preserving dubbing settings for any video.
4. Have a native speaker in each target market review the localized copy before it goes live, not just the automated translation.
5. Save the pipeline as a template once you're happy with the setup, so every future campaign reuses it instead of starting from scratch.
6. Push the approved localized ads back to their source platform and monitor performance by market the same way you would for any new creative.

Ads Engine sits inside ElevenLabs' creative platform plans; check current plan requirements for ad-account connections before you build out a full pipeline.

Tracking performance once you're running across markets

Once the same ad is live in five languages across three platforms, your reporting needs to catch up to that complexity, not just your creative production. Set up separate performance tracking per language and per platform from day one rather than lumping all localized versions together under one campaign name; a version that's genuinely underperforming in one market will get hidden in an aggregate number that looks fine overall. Watch specifically for a localized version that gets the translation right but still underperforms, since that's usually a sign the underlying message or offer doesn't resonate in that market the way it does at home, which is a positioning problem localization can't fix on its own, no matter how accurate the dubbing sounds.

When is an agency still the better call?

For genuinely new creative concepts, campaigns that need real strategic thinking about positioning, audience, or an idea nobody's tried yet, an agency's creative and strategy work is still doing something this tool isn't built for. Ads Engine's job starts after that concept already exists: speeding up how fast it gets adapted, localized and pushed live across markets and platforms.

Common mistakes worth avoiding

Localizing a weak ad first. If the original creative isn't already converting well in your home market, localizing it five times just multiplies a mediocre result across five markets instead of one. Fix the concept at home first, then localize once it's proven. Second: treating every market the same once you've localized. A price, an offer, or a seasonal reference that works in one country can be irrelevant or even wrong in another (a "free shipping" offer that doesn't actually apply in that market, a holiday reference for a holiday that market doesn't celebrate), and the pipeline will happily localize the words without catching that the underlying offer itself doesn't translate. Build a short market-specific checklist into your review step, not just a language check. Third: skipping the review on later campaigns once the pipeline feels reliable. The native-speaker review matters just as much on campaign 20 as campaign 1, since a new product, a new offer or a new market each reintroduces the same risk the review step exists to catch. For voiceover in specific markets, see making AI voiceovers in Arabic, Hindi and English.

When should you skip this?

If you're only running ads in one language and one platform, the localization and multi-platform-push features here aren't doing much for you, and a simpler creative tool might suit the actual job better. This tool earns its keep specifically at the point where you're managing creative across several languages or several ad platforms at once. To test many versions of one ad without overloading your budget, see how to test 20 ad variations.

How I'd approach this

For a business running ads in a handful of markets, Ads Engine's own pipeline setup is the right starting point. Where I come in is when the ad creative needs to connect to something more specific: pulling product data straight from your catalog to auto-generate localized ad copy per SKU, or routing approved creative through your own review workflow before it ever reaches the ad platform. That's a build on top of what Ads Engine does by default, not a replacement for it.

A realistic version of that: an ecommerce catalog with hundreds of SKUs, each needing a localized ad for a handful of markets, pulling product name, price, stock status and a short feature line straight from the product database into an ad-copy template per SKU, then feeding that into Ads Engine's localization pipeline automatically rather than someone manually building each ad by hand. The hard part isn't the localization itself at that point, Ads Engine already handles that; it's the pipe connecting your catalog's live data to the ad-copy template so a price change or a sold-out item doesn't need someone to remember to update dozens of ad variants by hand. That's the kind of connective build that turns a genuinely useful tool into something that runs itself.