> For the complete documentation index, see [llms.txt](https://helpdocs.ycloud.com/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.ycloud.com/help-center/integrations/channels/email/best-practices-for-email/separate-marketing-subdomain.md).

# Separate Marketing Subdomain

To ensure that critical customer-specific emails are not affected by promotional emails, we recommend segmenting your domain's IP based on functionality. This will help optimize email delivery.

A domain name is unique to your website, such as [*ycloud.com*](http://ycloud.com/). A subdomain is a subset of the main domain, identified by a prefix.

Subdomains have different reputations from the main domain. This means that if someone in your company accidentally sends a marketing email without an unsubscribe link and the recipient complains, the reputation of your main domain will remain unchanged.

For example, you can use the following subdomains for different functions:

* <_marketing@marketing.company.com> for marketing emails\_
* <_support@support.company.com> for transactional emails, such as password resets and order confirmations\_.


---

# 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://helpdocs.ycloud.com/help-center/integrations/channels/email/best-practices-for-email/separate-marketing-subdomain.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.