> For the complete documentation index, see [llms.txt](https://docs.2checkout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2checkout.com/marketing/emails/email-variables.md).

# Email variables

## Overview

***

Use email variables to customize shopper emails for your specific scenarios.

Refer to the email list below to see each email theme and draft variables, their description, and preview values.

## Requirements

***

Editing the 2Checkout emails requires using a variation of the [Smarty version 3 syntax](http://www.smarty.net/syntax_comparison). Namely, instead of using { and } as delimiters, use \[% and %], as shown in the example below.

```
[%$FIRST_NAME_BILLING%] instead of {$FIRST_NAME_BILLING}
```

## Customize theme and email variables

***

Customize theme variables to better reflect company-specific details in your emails, such as your logo, address, or support information.

To customize the variable values, follow the steps below.

1. Create a new email theme (from scratch or from an existing one) or a new email draft.
2. Click the **Manage variables** button in the editor.
3. Modify the values in the **Test value** column according to your preferences.
   * You can undo the changes by clicking the **Undo** icon next to the value field.
4. Click **Save** and use the **Preview** feature to see how the new variable values will be displayed to your shoppers.

### Use case: Customize support information

***

To customize the support information displayed in your emails, follow the next steps.

1. Open the *Email editor* and click **Manage variables**.
2. Find or search for the following email variables:
   * MERCHANT\_SUPPORT\_EMAIL
   * MERCHANT\_SUPPORT\_PHONE
3. Modify the test values of these variables to reflect the changes you wish to perform. Click **Save**.
4. Use the **Preview** feature to see how the new variable values will be displayed to your shoppers.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.2checkout.com/marketing/emails/email-variables.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
