A merge tag is a placeholder inserted into an email template that gets automatically replaced with a subscriber's actual data, like their first name or last order number, at the moment the email sends.
Anyone asking what is a merge tag for the first time usually pictures something more complicated than it actually is, at its core it’s just a stand-in that gets swapped for real data right before delivery.
How the Placeholder Actually Works
A merge tag looks something like {{first_name}} or {{last_order_date}} inside the template editor, and it never appears that way to an actual recipient. When the email sends, the platform swaps that placeholder for the specific subscriber’s real data pulled from their contact record, so one template produces a thousand slightly different emails, each addressed and populated correctly for the individual reading it.
Merge Tag Examples Beyond a First Name
{{first_name}}— the most common example, inserting a subscriber’s name into a greeting.{{last_purchase_item}}— referencing the specific product someone bought most recently.{{loyalty_points_balance}}— showing a subscriber’s current points total in a loyalty email.{{cart_items}}— pulling in the actual products sitting in an abandoned cart.
Each of these pulls from a different data field, but they all work through the same underlying mechanism, a placeholder swapped for real data at send time.
Merge Tag vs Personalization Token
Merge tag vs personalization token is mostly a naming difference rather than a functional one. Some platforms use “merge tag,” others use “personalization token” or “dynamic field,” but all three describe the same mechanism: a placeholder resolved into real subscriber data before the email actually goes out. Knowing this helps avoid confusion when switching platforms or reading documentation that uses a different term for a concept already familiar under another name.
What Happens When the Data Is Missing
Merge tag email marketing setups need a fallback for a real, common problem: what displays if a subscriber’s record is missing the requested field. An email reading “Hi ,” with a visibly blank space where a name should be, looks broken and unprofessional. Well-built merge tags include a default fallback value, “Hi there,” instead of a blank, so a gap in the data doesn’t turn into a visible mistake in front of the subscriber.
Related terms:
Adflipr’s email builder supports merge tags pulling from customer and order data synced directly from Shopify or WooCommerce.
