> 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/campaign-execution-and-monitoring/campaign-checklist.md).

# Campaign Checklist

Must do configuration checks before activating a campaign

{% stepper %}
{% step %}

#### Domain is setup correctly

Before sending emails to your contact list, you’ll need to set up your email domain. You can find detailed setup instructions [here](/humanic/getting-started-with-humanic/domain-setup/setting-up-mail-domains-in-humanic.md).

Keep in mind that new domains must be **warmed up gradually** before sending large volumes of emails. Start small — a few hundred emails per day — and increase your sending volume by about 20% each day.

Sending too many emails too quickly can harm your domain’s reputation, causing your messages to land in spam folders instead of inboxes.
{% endstep %}

{% step %}

#### Sender email and name is correct.

Ensure that the sender email address is correctly set, including the appropriate name and the company's primary domain. Using alternate or sister domains can increase the likelihood of your email being flagged as spam.

If you have a different email address where you want to receive all the replies you can configure the reply-to setting.
{% endstep %}

{% step %}

#### Unsubscribe link is present

The unsubscribe link is clearly visible and fully functional. You can manage the global settings for the unsubscribe link in the Settings tab on the left navigation menu.
{% endstep %}

{% step %}

#### Test email looks good

Be sure to send a test email to yourself and review it thoroughly for broken links, fonts, styling, and spacing. Also, double-check that all social media links and the unsubscribe button in the email footer redirect to the correct web pages.
{% endstep %}

{% step %}

#### First name is personalized

Each email sent through Humanic should include the recipient’s name for better results. You can add this by inserting a personalization parameter, such as user.first\_name, into the email body. For step-by-step instructions, refer to the [Activating the Campaign section](/humanic/advanced-features/hyper-personalization.md).
{% endstep %}

{% step %}

#### The right audience is selected

The system provides several ways to define which users should be included in an email campaign. The easiest option is uploading a .csv file with user data. 

For more advanced segmentation, you can connect your Data Warehouse, Segment, or Amplitude and many other tools to dynamically select the right users for each campaign. To find out more please setup a [full demo](https://cal.com/gethumanic.com/30min).
{% endstep %}
{% endstepper %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://humanic.gitbook.io/humanic/campaign-execution-and-monitoring/campaign-checklist.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.