> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/references/references/email/transactional-sendouts.md).

# Transactional sendouts

eMarketeer has a built-in consent management system that tracks who you can send marketing emails to. If a contact has withdrawn consent for marketing emails, the email is stopped and not sent.

In some cases the email you want to send is not a marketing email, and you need the contact to receive it regardless of their consent settings. Examples include:

* Important service information to customers
* Confirmation emails
* Delivery of requested information

To send an email that overrides the consent settings, mark the send-out as a "transactional email".

Sending marketing emails without consent is illegal. Use this setting only if the contact truly needs the information or is waiting for it.

## Sending an email manually from a campaign

You see this setting when addressing your email in the standard send-out screen.

<div align="left" data-with-frame="true"><img src="/files/TGIodEFm9v9QIWS1HY02" alt="Send-out screen with the transactional email setting highlighted"></div>

## Sending an email in a Journey

When you add the "Send email" step in a Journey, you also have the option to ignore consent by choosing "transactional email".

To decide whether to use transactional email in a Journey, ask yourself: is the contact expecting or waiting for this email? If yes, you can use a transactional email.

Common scenarios:

* Delivery of requested material, for example an e-book download
* Confirmation of a subscription or registration
* Thank-you emails

When not to use a transactional email:

* Drip campaigns that send several emails over time
* Nurture campaigns
* Typical marketing emails that are unsolicited


---

# 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:

```
GET https://support.emarketeer.com/references/references/email/transactional-sendouts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.