# Step 2 - Technical Setup

{% stepper %}
{% step %}

### **💡** Goals

* Choose the names of your sending subdomains
* Choose the name of your tracking subdomain(s)
* Optional: Add support for Apple's Private Relay
* Optional: Add support for BIMI
* Optional: Set up Google Postmaster Tools and a DMARC monitoring tool
  {% endstep %}

{% step %}

### 📌 Deliverables

DNS records for each subdomain, provided by Batch implementation team upon request.
{% endstep %}
{% endstepper %}

Getting your subdomain up and ready to send emails with Batch is a simple task.\
You will find below all the steps you need to take to send your first emails:

## Step 1 - Sending Subdomains Setup <a href="#h_ff47e3f401" id="h_ff47e3f401"></a>

### → Sending Subdomain Name <a href="#h_a0be4f59c4" id="h_a0be4f59c4"></a>

First, you will need to define the subdomains you will use to send emails with Batch.

Consider using one subdomain per email activity at least.

For example:

* `service.domain.com` for transactional automations
* `hello.domain.com` for marketing automations
* `news.domain.com` for email campaigns

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2FpFNAZ5JQtUWGhqngAABD%2Fdeliverability_ip-pools_310325.png?alt=media&#x26;token=ee85c6b9-9f89-42fe-a43d-14efb59e308e" alt="" width="563"><figcaption></figcaption></figure>

You might need to create additional subdomains in certain cases:

* `service.domain.com` for your main website and `service.domain.fr`, if you have a French website
* `news.domain.com` for global newsletters and `noticias.domain.com` to separate the reputation of your newsletters in Spanish (e.g., if you know you usually get issues with that audience)

In any case, the subdomain used by Batch must:

* Be new and have a neutral reputation
* Be used exclusively for emails sent from Batch
* Be attached to your website's domain

You will find more information on that matter here: [Email sending structure & domain consistency](https://doc.batch.com/guides-and-best-practices/email-deliverability/email-authentication-and-sending-structure/sending-infrastructure-best-practices).

### → Email Authentication <a href="#h_3ef23a1ae0" id="h_3ef23a1ae0"></a>

All the emails sent from Batch must use SPF, DKIM and DMARC (see more here: [Understanding email authentication](https://doc.batch.com/guides-and-best-practices/email-deliverability/email-authentication-and-sending-structure/email-authentication-spf-dkim-dmarc-and-bimi)).

Batch team will guide you through the setup process and provide DNS records your technical teal will add to your DNS zone (see more here: [Setting up a sending domain on Batch](https://doc.batch.com/guides-and-best-practices/email-deliverability/email-authentication-and-sending-structure/sending-subdomain-setup-and-troubleshooting/setting-up-a-sending-subdomain)).

{% hint style="warning" %}
If you allow users to sign up with Apple, you may also need to add support for [Apple's Private Relay](https://help.batch.com/en/articles/6955373-setting-up-email-delivery-to-apple-s-private-relay).
{% endhint %}

### → Optional - BIMI <a href="#h_f7940d43f9" id="h_f7940d43f9"></a>

[Brand Indicators for Message Identification (BIMI)](https://bimigroup.org/) is an email specification that allows authenticated senders to display their logos within supporting email clients, improving brand recognition.

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2Fa84eEHeqsZsYaM5i3zSs%2Fdeliverability_bimi_310325.png?alt=media&#x26;token=2a70dce8-477a-4b00-ac7e-22e0a96c2843" alt="" width="563"><figcaption></figcaption></figure>

BIMI adds value for brands that want to stand out in the recipient's inbox or that are more likely to be targeted by phishing campaigns (e.g. finance, insurance, etc). Note that BIMI implementation is optional and not all email providers currently support it (see list of [providers supporting BIMI here](https://bimigroup.org/bimi-infographic/)).

{% hint style="info" %}
Implementing BIMI is possible with Batch. It supposes additional costs to get a renewable Verified Mark Certificate.
{% endhint %}

## Step 2 - Choosing a Tracking Subdomain <a href="#h_66c078225b" id="h_66c078225b"></a>

We recommend using a dedicated click tracking subdomain for all the emails sent from Batch (e.g. `click.domain.com`) that will be aligned with your root domain (e.g. `domain.com`).

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2FgBwwqj3uBoh75WzvCAsG%2Fdeliverability_content-alignment_310325.png?alt=media&#x26;token=655208b5-11de-4174-bedb-e5a9a553050d" alt="" width="563"><figcaption></figcaption></figure>

If you send emails from news.domain.fr and news.domain.com, make sure you have two different tracking domains (e.g. `click.domain.fr` and `click.domain.com`).

## Step 3 - Monitoring Your Email Activity <a href="#h_ccd2fd2c90" id="h_ccd2fd2c90"></a>

We strongly recommend you set up additional tools to keep track of your domain reputation and DMARC issues:

* **Domain reputation**: Setting up Google Postmaster Tools for your newly created subdomains is important to monitor your domain and IP reputation during the warmup phase.
* **DMARC monitoring**: Setting up a DMARC monitoring tool is important to know when emails are being sent with a bad SPF or DKIM authentication. This could allow you to identify attacks or phishing campaigns.

## Next step <a href="#h_89991a664a" id="h_89991a664a"></a>

You should now be able to send your first test emails internally.

Let's take a look at your current list hygiene and recipients base quality.

{% content-ref url="step-3-list-hygiene-review" %}
[step-3-list-hygiene-review](https://doc.batch.com/guides-and-best-practices/email-deliverability/domain-and-ip-warm-up/step-3-list-hygiene-review)
{% endcontent-ref %}