> 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
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]`.
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:
`Hello [first_name]!
`
When the **Email** is exported to Mailchimp, Alpaco will replace the `[first_name]` tag with the correct Mailchimp tag, `*|FNAME|*`:
`Hello *|FNAME|*!
`
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://documentation.alpaco.email/account-settings/merge-tags.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.