Provider documentation checked on 8 November 2026. Account-generated values, entitlements and current support remain deployment prerequisites.
Reserve the right names
Beamery can send recruitment campaigns with customer-domain authentication, but a domain connection is more than a cosmetic sender label. Begin with the recruiting campaign owner, the DNS administrator and a security contact. Record the intended From address, domain, chosen technical subdomain and whether branded tracking is required. Inspect existing DNS at each proposed name before connecting anything.
A familiar name such as careers may already serve a recruitment website. Do not replace that service with a mail-related CNAME. Choose an unused label with the domain owner instead. The name selected for technical routing need not become the visible mailbox address used by recruiters. Beamery's authentication fact sheet explains this distinction and identifies SendGrid as its delivery system.
Complete the custom-domain flow
References: RFC 1034 §3.6.2.
The documented route is Beamery Settings > Email Settings > Custom Domain > Add Your Domain. Supply the domain and subdomain, select Connect Domains, then give the generated records to the DNS administrator. Return to that screen and select Verify after publication. For multiple domains, the domain menu can choose a default. Custom-domain instructions
Copy the generated account values rather than the sample numbered SendGrid hosts in the fact sheet. Its sample illustrates three CNAMEs, including two DKIM selectors; it is not an account-specific prescription. A CNAME delegates resolution at that owner, so inspect any existing record before replacing it. Publish through the authoritative DNS service, which may differ from the registrar.
Beamery also describes generated Inbound Parse values after verification. Treat changes there as a separate routing decision and preserve the current configuration. The existence of this section does not authorize moving the organization's ordinary inbound mailbox MX records.
Review branded links separately
The documented link workflow is Email Settings > Branded Tracking Links > Add a Branded Links, followed by domain/subdomain entry, Add Link, DNS publication and Verify. Authentication and link branding have distinct verification screens. A working tracking link is not proof that a received message passes DMARC, and a passing signature is not proof that the link destination works.
Original release worksheet: use one row per campaign domain, recording the chosen From identity, generated record owners, default-domain decision, link-branding status and accountable recruiter. Keep account-generated values and screenshots in a private change record. Avoid candidate information in technical test messages.
Test the campaign recipients will receive
References: RFC 9989 §4.4, RFC 6376 §6.
Send a harmless campaign to a controlled mailbox using the intended workflow. Capture the trusted receiving system's authentication results, visible From, envelope sender and DKIM signing domain and selector. Evaluate alignment against the actual From domain. Also follow an approved test link and verify its expected destination and HTTPS behavior without entering real candidate data.
Illustrative scenario: the team authenticates a new recruitment domain but leaves another domain selected as default. A successful DNS check cannot tell you which identity the next campaign uses. The received message and selected campaign settings resolve that ambiguity; adding a second copy of the same DNS records does not.
Maintain an explicit recovery path
If a test fails, pause the affected campaign and restore the last approved domain or link selection. Keep existing valid records until their dependencies are understood. Recheck after changing the default domain, DNS provider or tracking configuration. If policy prohibits sending on the apex domain, engage Beamery's technical team rather than improvising unsupported settings.
This guide reflects documentation reviewed on 8 November 2026. The worksheet and scenario are original operational examples; no Beamery account, DNS update or campaign delivery was executed here.