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

# Email Marketing

Create, schedule, and measure email campaigns for your customers.

## Email Marketing

Email Marketing is available from the **Marketing** tab. Create campaigns that keep customers engaged and help grow your business.

### What you can do

* Send bulk campaigns to your customers.
* Add inline images to campaign emails.
* Send a campaign immediately or schedule it for later.
* Track opens and clicks for each campaign.
* Choose from six ready-made templates or save your own.

### Choose your audience

Send a campaign to:

* All customers.
* Customers who joined within the last 15, 30, or 90 days.
* Specific customers or customer teams.

### Availability

Email Marketing is available on the **Partner** plan. Other plans show a prompt to book a call when you try to send a campaign.


---

# 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://uni.fotello.co/marketing/email-marketing.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.