Dynamic text replacement is a PRO front end feature. It rewrites the visible copy per visitor, in the browser, so it works correctly on a page served from a full page cache.
Switching it on:
It is on by default once PRO is active. There is a toggle for it on the PRO tab under PRO Features.
Where it applies:
Three fields are processed: the headline, the sub-line and the button text.
The tags you can use:
- {utm_source}, {utm_medium}, {utm_campaign} and {utm_term}, taken from the URL
- {referrer}, the full referring URL
- {referrer_domain}, just the domain, with www stripped
- {date}, today's date in the visitor's own locale format
- {day}, the name of the day in the visitor's locale
- {url_name}, where name is any query parameter on the URL. For example {url_city} reads the city parameter.
Fallbacks:
Add a fallback after a colon and it is used whenever the value is missing or empty. For example Welcome, {utm_source:friend} visitor reads Welcome, newsletter visitor for tagged traffic and Welcome, friend visitor for everybody else.
Always set a fallback. A visitor who arrives with no UTM values should still read a complete sentence.
A worked example:
Run an advert with utm_source=facebook and utm_campaign=springsale, then write your popup headline as Your {utm_campaign:special} offer from {utm_source:us}. The message matching between the advert and the popup is what lifts the conversion rate, because the visitor never feels handed off to a stranger.
A tag that does not match anything known is left alone rather than blanked, so a stray curly brace in your copy will not silently eat a word.