Multi-Domain Sending & Sender Identities for Agencies

Run campaigns for several brands from one MailInApp account. Verify each client's own domain once, create a sender identity per brand or per kind of email, and set a default on each contacts list, so every send to a client's list goes out under the right name, address and links without picking it each time.

Subject

Your spring collection is here

Verify more than one sending domain on one MailInApp account and give each brand its own sender identities. One account then sends as several client brands, each with its own domain, from-addresses, replies and tracking links.

An agency sending for several clients wants each email to come from the brand its readers know. Verify each client's domain once, and everything after it, from the from-address to the links, follows that brand.

Verify each client's domain

Settings → Domains lists every domain on the account. Each one has its own DNS records, verification status, from-address and receiving settings. Set default picks the domain a send uses when nothing more specific is set. See Multiple domains & sender identities.

A sender identity per brand or purpose

On a verified domain, a sender identity is a name, an address and a reply-to: [email protected] for receipts and [email protected] for newsletters, both on the same domain, each showing readers its own name and address.

The right sender, automatically

A send uses the most specific sender set, in this order:

  1. A recurring send's own sender.
  2. The email's own sender, picked in the Send panel.
  3. The audience list's default sender.
  4. The account's default sending domain.

Set each client's contacts list to that client's sender once, and every send to the list goes out under the right identity. The Send API takes a senderId, or a from address on any verified domain, for each call.

A reader who hovers a link or forwards an email sees its domain. From the Lite plan up, a custom tracking domain puts the live view, click and open links on a subdomain of the client's domain, with one CNAME record and the certificate set up for you. A custom portal domain does the same for landing pages and the member portal.

Keep every brand's lists healthy

Each domain has its own DKIM, SPF and DMARC records, and the account's bounces and complaints are counted together. Keep every client's list clean: MailInApp verifies each address as it's imported, and a sunset policy re-engages or rests contacts who have gone quiet.

When a client needs its own company

A client with its own plan, its own Stripe account for checkout or its own team gets its own company. Your staff move between companies with the company switcher, from one login. See White-label agency workflows.

Getting started

Verify each client's domain under Settings → Domains, create the sender identities each brand needs, and set the default sender on each client's contacts list. Then add a custom tracking domain so the links match too.

Watch: book calls and get client sign-offs by email

A creative agency connects its client list, its calendar and its team, then lets clients book a call, pick a direction and approve the work with one tap from the inbox, with every answer in Insights.

A typical build-and-send sequence

  1. 1

    Verify each client's domain

    Add a sending domain per client under Settings → Domains. Each one has its own DNS records, status and from-address.

  2. 2

    Create a sender identity per brand or purpose

    On a verified domain, add identities such as orders@ for receipts and hello@ for newsletters, each with its own name and reply-to.

  3. 3

    Set the right default

    Pick a sender on an email, on a recurring send or as a contacts list's default, so a client's sends use the right identity automatically.

  4. 4

    Brand the links

    From the Lite plan up, add a custom tracking domain so every link in the email shows the client's own domain.

Frequently asked questions

How many sending domains and sender identities can one account have?

Each plan includes a number of each, from one domain and one identity on Free up to unlimited on Business and Enterprise. See pricing for the exact numbers.

If I don't pick a sender for a send, which one is used?

The most specific one set: a recurring send's own sender or the email's own sender first, then the audience list's default sender, then the account's default sending domain.

Is each client's domain authenticated on its own?

Yes. Each verified domain has its own DKIM, SPF and DMARC records and its own from-addresses. The account's bounces and complaints are counted together, so keep every client's list healthy with email verification on import and a sunset policy.

Can the Send API use a specific client's sender?

Yes. Pass a senderId, or a from address on any of the account's verified domains, for full control on each call.

What happens when I delete a sender identity?

Anything that used it switches to its domain's default from-address, so recurring sends and lists keep sending.

When should a client get its own company instead?

When the client needs its own plan, its own Stripe account for checkout or its own team. Your staff move between companies with the company switcher, from one login.

Build this in the studio

Start on the free plan — every interactive block and the full fallback engine are included on every tier.