> For the complete documentation index, see [llms.txt](https://documentation.alpaco.email/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.alpaco.email/account-settings/merge-tags.md).

# Merge Tags

{% hint style="info" %}
Only users with role **Admin** can edit Merge Tags
{% endhint %}

Many ESPs have support for merge tags or personalization variables, for example to write out a customers first name in the email.

The Alpaco Platform supports a Merge Tag feature, where you can add Merge Tags in Alpaco and define the matching merge tag code in the ESP/Integration.

### Creating and using a Merge Tag <a href="#creating-and-using-a-merge-tag" id="creating-and-using-a-merge-tag"></a>

In the below example, we have added a Merge Tag with the name `First Name`. Alpaco automatically creates a tag that you can use within your templates to reference this merge tag, in this case it's `[first_name]`.

![](https://4158541773-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUZwvCYi7VuSyayWGoc6M%2Fuploads%2FCdQLPWxFkVbiU8FjqdaN%2FSk%C3%A6rmbillede%202023-10-04%20173847.png?alt=media\&token=6b1df6d2-eda8-4c66-b422-f4ac94076772)

For this newly created Merge Tag, I have to specify the corresponding tag in your Email Service Provider(ESP). In this example we'll use Mailchimp:

Now I can go ahead and use the tag `[first_name]` anywhere in my Template code:

`<h1>Hello [first_name]!</h1>`

When the **Email** is exported to Mailchimp, Alpaco will replace the `[first_name]` tag with the correct Mailchimp tag, `*|FNAME|*`:

`<h1>Hello *|FNAME|*!</h1>`