Your LinkedIn ad talks to operations directors juggling staff across five locations.
Your retargeting ad reaches people who already looked at pricing.
Both land on the same headline: “Better software for growing businesses.”
Changing a word might help. But these campaigns may need to answer different questions.
One visitor is trying to understand whether you solve their problem. Another may be deciding whether to buy.
What dynamic text replacement does well
Dynamic text replacement changes fields in page copy using values passed in the ad link.
You write a template, choose which parts can change, and provide a default when the expected value is missing.
“Book a plumber in [city]” is a straightforward example. Same service. Same next step. Different location.
A template can contain several changing fields. The useful question is whether the resulting copy still fits the visitor's reason for clicking.
If it does, keep it simple. You don't need to rewrite a page because a parameter can do the job.
Check the allowed values, missing parameters and sentence grammar. And make sure every location or service you name is one you actually cover.
When the template stops fitting
Imagine an ad that says: “Still filling shifts in a group chat?”
It earns a click from an operations director.
The page says: “Your operations team deserves better software.”
You've changed the audience label. You haven't carried through the problem that caught their attention.
A more useful version might be:
Headline: “See open shifts across every location.”
Supporting copy: “Give managers one view of coverage so they can spot gaps and arrange replacements.”
Button: “See the scheduling workflow.”
That's an illustrative example, and every claim would need to match the product. But the point is clear: the headline, explanation and next step work together.
For the pricing retargeting campaign, you might instead address a purchase question the ad raises, such as what's included or how setup works.
Write to the campaign's promise. Don't assume everyone in a retargeting audience has the same objection.
Campaign-specific copy keeps the page
You can write several versions of the headline, supporting text and call to action without building several pages.
Campaign tags in the ad link select the appropriate version. Visitors without a matching campaign see the original.
Those tags tell you the context of the click. They don't identify the visitor or prove what they're thinking.
The distinction is mainly how you author the message. Both approaches can use URL parameters.
| Question | Dynamic text replacement | Campaign-specific copy |
|---|---|---|
| What do you write? | A template with changing fields | A complete version of selected copy |
| When does it fit? | The same message works with a few substitutions | The campaign needs a different explanation or next step |
| What needs review? | Values, defaults and how substitutions read | Every version's claims, wording and CTA |
More copy means more responsibility
A rewritten paragraph has more room to go wrong.
It can invent a capability, imply a discount or contradict your pricing page. Generated copy needs the same scrutiny as anything you'd publish yourself.
Before a version goes live, check three things: does it continue the ad's promise, is every claim true, and does the button lead where it says?
Review the variants again when the offer changes.
And recognise when copy isn't enough. A different product, application form or buying process may deserve its own landing page.
Where Lens fits
I build Lens for reviewed campaign-specific copy on an existing page.
You keep the underlying page, approve the versions and match them to campaign links. The original remains available as the fallback and for a holdback comparison.
That last part matters. A more relevant-sounding headline is still a hypothesis. Compare conversions and read the counts behind the rates. A few clicks won't settle it.
See how Lens works or view pricing.
Start with two campaigns sharing one page. Read each ad beside the opening copy.
If both make the same promise, a template may be enough. If the promises differ, write the version each campaign needs.