> 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-monitor.md).

# Email monitor

## Overview

***

The 2Checkout email monitor gives you greater visibility on the emails that your customers receive from 2Checkout. You can choose to receive emails from the following categories by simply entering the email address that you want the email forwarded to:

* Order confirmations
* Software delivery
* Renewal notifications
* Follow-up emails
* Purchase order emails

## Availability

***

Available to all 2Checkout accounts.

## Workflow

***

To enable the email monitor:

1. Log into your 2Checkout account in the [Merchant Control Panel](https://secure.2checkout.com/cpanel).
2. Navigate to *Dashboard → Integrations → Webhooks and API.*
3. In the *Webhooks and API* section, scroll down to the *Notifications* section and check the **Email monitor** box to enable this feature.
4. Select the categories of emails that you want to receive, then enter the email addresses in the **To** field. You can choose to send the emails as **Carbon copies** or **Blind carbon copies**.&#x20;
5. Click **Update** to save the settings.

{% hint style="warning" %}
If you need to enter multiple email addresses, you can separate them using a comma. The To field is limited to 250 characters, including commas. For greater flexibility, recipients of different email categories do not need to be the same.
{% endhint %}


---

# 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-monitor.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.
