> For the complete documentation index, see [llms.txt](https://docs.parameter1.com/base-cms/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parameter1.com/base-cms/newsletter-management/new-framework/campaign-deployment.md).

# Campaign Deployment

There are two different ways to deploy newsletters depending on which ESP you use and your own personal preferences.

1. [**Using Base for ESP Integration**](/base-cms/newsletter-management/new-framework/campaign-deployment/using-base-for-esp-integration.md)
   * *Base Platform* has an integrated campaign deployment interface where you can preview, test, and schedule newsletter deployments.  
   * Currently only supports Omeda integration.  If another ESP is being used for deployment, you can follow the instructions for [HTML Extraction](/base-cms/newsletter-management/new-framework/campaign-deployment/extracting-the-html-for-deployment.md).
2. [**Extracting HTML to insert into third-party software**](/base-cms/newsletter-management/new-framework/campaign-deployment/extracting-the-html-for-deployment.md)
   * Depending on your workflow, you may prefer to only use *Base Platform* for scheduling content to your newsletters, and extract the source code to paste into a third-party's ESP software.  If that's the case, you can follow the instructions on how to extract the source code [here.](/base-cms/newsletter-management/new-framework/campaign-deployment/extracting-the-html-for-deployment.md)


---

# 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.parameter1.com/base-cms/newsletter-management/new-framework/campaign-deployment.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.