> For the complete documentation index, see [llms.txt](https://docs.mailofly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mailofly.com/product-guides/campaigns.md). # Campaigns A **campaign** ties together an audience (segment), a message (template), and a **schedule**: send manually, once at a time, or on a recurring rule. Each execution creates a **run** with delivery stats. ## What it is You describe who gets mail, what they see, and when (or whether) automation should fire. Until segment and template are set and the schedule is valid, the campaign is “incomplete” and cannot send. ## How it helps * **Clear blast scope** — always tied to one segment, so you know exactly which list received each send. * **Automation-ready** — recurring schedules and “new contacts” style flows reduce repetitive work. * **Traceability** — runs and mail logs connect back to the campaign for support and reporting. ## How to use it In [Campaigns](https://www.mailofly.com/user/campaigns), create a campaign, pick segment and template, configure schedule, then use **Send now** or wait for the scheduled time. Choose sending accounts if you want to override defaults. ### Schedule types (summary) * **Manual** — you trigger each send. * **Scheduled once** — single datetime in ISO 8601. * **Recurring** — interval + day/week/month unit. * **Recurring for new contacts** — automation oriented toward newly added segment members (see in-app copy for exact behaviour). ## Compared to one-shot “broadcast” tools Campaigns are first-class objects with schedule metadata and run history—not only a one-off send. That makes API automation and auditing easier: the same campaign can be updated, re-sent, or inspected over time. ## Related * [REST API: Campaigns](/rest-api/campaigns.md) * [Campaigns in the app](https://www.mailofly.com/user/campaigns) --- # 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.mailofly.com/product-guides/campaigns.md?ask=&goal= ``` `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.