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

# Email Marketing

CrowdWork's email tools let you reach your patrons without leaving the Dashboard. Build a newsletter or promotion in a drag-and-drop editor, pull live show and class details into the message, send to the right slice of your audience, and see how it performed — all in one place.

Email lives in the **Emails** section of your Dashboard sidebar. A single email you build and send is called a **campaign**.

***

## The two lanes: Marketing and Transactional

Every campaign is one of two types. You choose the type when you start a new campaign, and the type shapes how you build it and who receives it.

### Marketing

Newsletters, promotions, and show or class announcements — anything designed to bring patrons back.

* Built in a **drag-and-drop block builder** with headings, images, buttons, and live event blocks
* Sends only to patrons who **opted in to your newsletter**
* Includes an **unsubscribe footer** so patrons can opt out
* Gets **open and click tracking** plus **revenue attribution**, so you can see what each campaign earned

### Transactional

Operational, service-style messages — roster changes, venue updates, schedule postponements, and other "you need to know this" notices.

* Composed in a **simple rich-text editor**
* Reaches **every targeted patron**, whether or not they opted in to your newsletter, because it's service information rather than promotion
* Has **no unsubscribe footer**

{% hint style="info" %}
**Not sure which to use?** If the message promotes something or invites patrons back, it's Marketing. If it's information a patron needs about something they already bought or signed up for, it's Transactional.
{% endhint %}

***

## Where to find it

Open the **Emails** section in your Dashboard sidebar. It contains:

| Area              | What it's for                                                                 |
| ----------------- | ----------------------------------------------------------------------------- |
| **Campaigns**     | Create, draft, send, and review your emails                                   |
| **Segments**      | Save reusable audiences you can target again and again                        |
| **Suppressions**  | The do-not-email list — patrons who have bounced, complained, or unsubscribed |
| **Asset Library** | Images and files you reuse across campaigns                                   |
| **Templates**     | Saved starting points for new campaigns                                       |

***

## Who can use it

Email tools are part of the Dashboard, so staff with the right access to your theatre can use them. If a teammate can't see the **Emails** section, check their role under **Staff & Users**.

***

## The life of a campaign

Every campaign moves through the same stages:

1. **Draft** — choose the type, build the content, and set the subject, sender name, and reply-to address
2. **Send a test** — email a copy to yourself or a teammate to proof it before it goes out
3. **Send now** — confirm and send to your chosen audience
4. **Recipients resolved** — CrowdWork works out exactly who receives the campaign at send time
5. **Reports** — once sent, the campaign's performance appears in its report

{% hint style="info" %}
**Who actually receives it?** Your recipient count is resolved when you send, and it's often smaller than your full patron list. See [Choosing Your Audience](https://docs.crowdwork.com/for-theatres/email-marketing/choosing-your-audience) for why.
{% endhint %}

***

## Before you can send

Email sending turns on once your theatre has an established, genuine sales history. This protects inbox deliverability for every theatre on CrowdWork — a warm-up period keeps shared sending reputation healthy so your emails land where they should.

While sending is still being enabled, you can build and save campaigns; you just can't send yet. If your theatre has been selling tickets and you don't see sending enabled, [contact support](https://docs.crowdwork.com/contacting-support).

{% hint style="info" %}
**Sending limits grow with you.** Limits start lower and increase as your theatre builds a healthy sending track record. The current figures for your theatre are always shown in the composer when you send.
{% endhint %}

***

## Related Tasks

| Task                                              | Guide                                                                                                                |
| ------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| **Build and send a marketing campaign**           | [Building a Campaign](https://docs.crowdwork.com/for-theatres/email-marketing/building-a-campaign)                   |
| **Target the right patrons**                      | [Choosing Your Audience](https://docs.crowdwork.com/for-theatres/email-marketing/choosing-your-audience)             |
| **Manage unsubscribes and the do-not-email list** | [Suppressions & Unsubscribes](https://docs.crowdwork.com/for-theatres/email-marketing/suppressions-and-unsubscribes) |
| **Collect newsletter opt-ins at checkout**        | [Customizing Your Theatre Settings](https://docs.crowdwork.com/for-theatres/customizing-your-theatre-settings)       |
| **Track conversions and revenue events**          | [Tracking Pixels & Conversion Events](https://docs.crowdwork.com/for-theatres/tracking-pixels-and-conversion-events) |

***

## Need Help?

If you run into a situation this guide doesn't cover, [contact our support team](https://docs.crowdwork.com/contacting-support) from your Dashboard. We're here to help!


---

# 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://docs.crowdwork.com/for-theatres/email-marketing.md?ask=<question>&goal=<endgoal>
```

`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.