Default Headers for Dedicated Sending Domains

Modified on: Wed, 2 Sep, 2026 at 1:17 AM

Email Deliverability
Setting Default Headers (From Name & From Email) for Your Dedicated Sending Domain
A Default Header overrides the From Name and From Email set at the campaign or workflow level, so every email sent through your dedicated domain uses one consistent sender identity.
Overview

The Default Header sets a From Name and From Email for a dedicated sending domain. Once configured, it always overrides the From Name and From Email set on any campaign or workflow sent through that domain — regardless of what was typed into the campaign or workflow itself. If the Default Header is left blank, emails send using the From Name and From Email configured on the individual campaign or workflow instead.

1

When to Use a Default Header

Use Case 1
Enforce One Sender Identity Across Every Send

Set the From Name and From Email once at the domain level, and every campaign and workflow sent through that domain uses it automatically — even if a teammate types a different From Name or From Email into an individual campaign or workflow, the Default Header takes over at send time.

Use Case 2
Regulatory & Compliance Requirements

Industries with strict communication standards — such as finance and healthcare — can lock every outbound email to a single, approved sender identity by setting a Default Header, removing the risk of any individual campaign or workflow going out under an unapproved From Name or From Email.

2

Prerequisites

Before configuring a Default Header, confirm the following are in place.

Requirement 1
You're Working in a Sub-Account

Default Headers can only be set on dedicated sending domains managed within a sub-account. Agency-level domains do not support per-sub-account Default Header configuration.

Requirement 2
Your Dedicated Sending Domain Is Added and Validated

You must have completed DNS setup — including CNAME, DKIM, and SPF records — for your custom sending domain (e.g., email.yourbrand.com).

A green checkmark next to your domain under Settings → Email Service → SMTP Service → Dedicated Domain and IP confirms it is validated and ready.

3

Setting the Default Header (From Name & From Email)

The Default Header is configured per dedicated domain within a sub-account. Navigate to the location below to access the setting.

Navigation
Sub-Account Settings → Email Service → SMTP Service → Dedicated Domain and IP → Set Headers
Dedicated Domain and IP settings showing Set Headers option
Find your validated domain and click "Set Headers" to open the configuration panel.
Set Headers form showing From Name and From Email fields
How It's Applied

Once saved, the Default Header always overrides the From Name and From Email configured on any campaign or workflow sent through this dedicated domain — there is no condition attached, it applies to every send. If you leave the Default Header fields blank, emails are sent using whatever From Name and From Email is set at the campaign or workflow level instead.

4

How the Override Works in Practice

Step 1
Campaign or Workflow Configuration

When creating a broadcast or workflow email, you can still set a campaign-level From Name and From Email as usual. This is what will be used only if no Default Header is configured for the sending domain.

Step 2
Default Header Check at Send Time

At the moment the email sends, the platform checks whether a Default Header is saved for the dedicated domain. If one is set, it takes priority automatically — the campaign's or workflow's own From Name and From Email are ignored, not just used as a backup.

Step 3
Recipient Experience
  • If a Default Header is set, recipients always see that From Name and From Email — regardless of what was entered on the campaign or workflow.
  • Because the address comes from your authenticated sending domain, the email stays DMARC-compliant and is less likely to be rejected or flagged as spam.
5

Example: Default Header Set vs. Left Blank

Scenario

SettingValue
Dedicated Sending Domainemail.yourbrand.com (validated)
Default Header — From NameYourBrand Support
Default Header — From Emailsupport@email.yourbrand.com

Broadcast / Workflow Email Configured by the User

FieldValue
Campaign From NameJane from YourBrand
Campaign From Emailjane@email.yourbrand.com

What Recipients See at Send Time

Default Header Is Set — Always Applied

From: YourBrand Support <support@email.yourbrand.com>
The campaign's "Jane from YourBrand" name and address are ignored completely, even though they were correctly configured and properly aligned to the domain.

Default Header Is Left Blank

From: Jane from YourBrand <jane@email.yourbrand.com>
With no Default Header saved for the domain, the campaign's own From Name and From Email are used as configured.

How to Confirm It Worked

  1. Save a Default Header whose From Name and From Email differ from a campaign's configured values.
  2. Send a test broadcast or workflow email from that campaign.
  3. Open the received email and check the From address — it should match the Default Header, not the campaign's configured From Name or Email.
6

Best Practices & Considerations

A
Decide Before You Set It — It Overrides Everything

Because the Default Header overrides every campaign and workflow sent through the domain, confirm this is the sender identity you want used across the board before saving it. Any campaign-level From Name or From Email your team configures afterward will be ignored while the Default Header is active.

B
Monitor Replies

The Default Header's From Email can be any address on your sending domain, but ensure that mailbox is actively monitored or aliased correctly (e.g., support@yourbrand.com forwarding to the right team) so customer replies don't go unread.

C
Test Before Scaling

Send a small internal test to confirm the Default Header is being applied. Check that the From Name and From Email recipients actually see match your Default Header configuration — not whatever was typed into the campaign or workflow.

D
Tell Your Team It's Set

A Default Header silently overrides whatever From Name and From Email a teammate configures at the campaign or workflow level. Make sure anyone building campaigns or workflows on this domain knows a Default Header is active, so they aren't confused when their custom From address never actually gets used.

E
Segregate by Sub-Account

If you manage multiple brands or departments, create separate sub-accounts — each with its own dedicated domain and Default Header — for fully isolated sending control and reputation management.

7

Common Troubleshooting Scenarios

IssuePossible CauseResolution
"Set Headers" option is not visibleYou're in an agency-level view, or the domain is not validated under a sub-account.Switch to the correct sub-account. Add and validate a dedicated domain under Settings → Email Service → SMTP Service → Dedicated Domain and IP.
Emails failing to send from the dedicated domainDNS records (DKIM/SPF) are incomplete or incorrectly formatted.Double-check DNS entries for your sending domain. Use an online DKIM/SPF validator. Allow up to 48 hours for propagation before testing again.
A campaign's configured From Name/Email shows up instead of the Default HeaderNo Default Header is set for the domain, or it was saved with blank From Name/Email fields.Go to Settings → Email Service → SMTP Service → Dedicated Domain and IP → Set Headers and confirm both fields are filled in and saved.
Recipients see the wrong From Name or From EmailThe saved Default Header contains a typo or stray spaces.Re-open the Default Header for the domain and re-save it with the exact From Name and From Email you intend.
SSL certificate not issued for the sending domainMissing or incorrect CNAME/DNS records for domain validation.In Settings → Dedicated Domain, click "Edit DNS Info" and follow the instructions exactly. Wait for propagation before retrying verification.
8

Frequently Asked Questions

Q: Does the Default Header override every email, or only in certain situations?
The Default Header overrides every campaign and workflow email sent through that dedicated domain — always, not just as a backup. As long as a Default Header is saved, it takes priority over any From Name and From Email configured on a campaign or workflow, even if the campaign's own address was correctly configured. It is only skipped when the Default Header fields themselves are left blank, in which case the campaign's or workflow's own From Name and From Email is used.
Q: Can I set a different Default Header for each dedicated domain?
Yes. The Default Header is configured per dedicated domain. If your sub-account has multiple validated sending domains, each one can have its own independent From Name and From Email override.
Q: What happens if I don't set a Default Header?
If no Default Header is configured, each campaign or workflow sends using whatever From Name and From Email was entered on that specific send. Make sure every address your team uses is properly authenticated on your sending domain, since there's no override in place to fall back on.
Q: Does the Default Header apply to workflows, or only broadcast campaigns?
Both. The Default Header applies to any email sent through the dedicated domain, whether it's triggered by a broadcast campaign or by a workflow action.
Q: Does the Default Header affect the Reply-To address?
No. The Default Header only controls the From Name and From Email fields. If you have set a Reply-To address on your campaign or workflow, that Reply-To continues to be used regardless of the Default Header.
Q: Should the Default Header's From Email use the domain I validated?
Yes. The Default Header's From Email should sit on your validated dedicated sending domain (e.g., if your domain is email.yourbrand.com, use something like support@email.yourbrand.com) so it stays properly authenticated by the SPF and DKIM records you set up.
Q: Will contacts notice when the Default Header is used instead of the campaign's From address?
Yes — since the Default Header always overrides the campaign's configured From Name and From Email, recipients see the Default Header's sender identity rather than whatever was set on the individual campaign or workflow. If a specific send needs a different sender identity, leave the Default Header blank for that domain, or route that send through a separate dedicated domain that doesn't have one set.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article