> For the complete documentation index, see [llms.txt](https://humanic.gitbook.io/humanic/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://humanic.gitbook.io/humanic/marketing-vs.-transactional-emails.md).

# Marketing vs. Transactional Emails

Humanic enables you to send both **Transactional** and **Marketing** emails.

### [​](https://resend.com/docs/knowledge-base/what-sending-feature-to-use#what%E2%80%99s-the-difference-between-transactional-and-marketing-emails)What’s the difference between Transactional and Marketing emails? <a href="#whats-the-difference-between-transactional-and-marketing-emails" id="whats-the-difference-between-transactional-and-marketing-emails"></a>

#### [​](https://resend.com/docs/knowledge-base/what-sending-feature-to-use#what-is-a-marketing-email)What is a Marketing email? <a href="#what-is-a-transactional-email" id="what-is-a-transactional-email"></a>

A **Marketing email** is any email that is not transactional. These can be **promotional**, **informative**, or **general communication** messages.Marketing emails are regulated by laws like **CAN-SPAM** (US) and **CASL** (Canada), and **recipients must have the option to unsubscribe**.Examples of marketing emails:

* Promotional offers and discounts
* Newsletters
* Product updates

Marketing emails can be **1-to-1** (e.g., abandoned cart reminders) or **1-to-many** (e.g., newsletters).[​](https://resend.com/docs/knowledge-base/what-sending-feature-to-use#what-is-a-transactional-email)

#### What is a Transactional email? <a href="#what-is-a-transactional-email" id="what-is-a-transactional-email"></a>

A **Transactional email** is a message triggered by a user action or required for legal compliance. These emails are essential communications that users **cannot unsubscribe** from. Common examples include:

* Order confirmations
* Password reset emails
* Account notifications

Typically, transactional emails are **1-to-1** messages sent in response to a specific event.

### [​](https://resend.com/docs/knowledge-base/what-sending-feature-to-use#should-i-be-sending-a-transactional-or-a-marketing-email)Should I be sending a Transactional or a Marketing email? <a href="#should-i-be-sending-a-transactional-or-a-marketing-email" id="should-i-be-sending-a-transactional-or-a-marketing-email"></a>

While not exhaustive, here’s a table listing different examples of emails and the most appropriate type for each example.

| Type of Message    | Type of Recipient | Transactional | Marketing |
| ------------------ | ----------------- | ------------- | --------- |
| Order confirmation | Single            | ✓             | ⨯         |
| Password reset     | Single            | ✓             | ⨯         |
| Abandoned cart     | Single            | ⨯             | ✓         |
| Newsletter         | Multiple          | ⨯             | ✓         |
| Promotional offer  | Multiple          | ⨯             | ✓         |

{% hint style="info" %}
Humanic is built to send both Marketing and Transactional Emails
{% 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 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://humanic.gitbook.io/humanic/marketing-vs.-transactional-emails.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.