Email Domain Manager: Set Up and Verify Your Sender Domains Yourself 📬
Sending event emails from your own domain has been possible for a long time. Getting there hasn't. It meant a request to Support, a round trip with our Customer team, and zero visibility on whether your DNS records had actually landed. The Email Domain Manager moves that entire process into Studio: you add the domain, publish the records, watch each one turn verified, and hand the sender addresses to the right events. Yourself.
![]()
How it works
- Add your domain. In Organization Settings, open the Email Domain section and enter your domain. Studio generates the DNS records your provider needs to publish.
- Publish and track. Each record is checked independently and carries its own status — under verification, verified, or invalid — so you can watch propagation happen instead of guessing.
- Create your sender addresses. Once the domain is verified, build the addresses you'll actually send from (
hello@,registration@,support@) on top of it. - Scope them to your events. Decide which events and communities can use each address. Event and Community Managers then pick it from the dropdown in their own settings (Emails > Sender address).
Deliverability, in plain sight
The manager doesn't only confirm the domain is yours. It shows you what stands between your emails and the inbox.
- Record-level diagnostics. Authentication, DMARC policy, and MX records are each checked and flagged on their own, so you fix the one that's broken instead of restarting the whole setup.
- A clear invalid state. A record that fails validation says so, in the same screen where you'd correct it. No support thread to find out why a magic link never arrived.
- Status in real time. Your IT contact publishes a record, your event manager refreshes, and the status moves. Nobody has to read DNS values back to anyone over email.
Assign once, cover the whole series
- Community-level in one action. Enable a sender address for a community and every event inside it can use it.
- Future events inherit it. Create a new event in that community later and the address is already attached, so nothing quietly reverts to
noreply@swapcard.comon send day. - Or stay granular. Scope an address to specific events only when a client, sponsor, or sub-brand needs its own sender.
- Verified once, shared across the group. Enterprises running several organizations under one umbrella don't re-verify the same domain for each one.
- Deletion is safe. Remove a sender address and every event using it falls back to the default Swapcard address. Communications never break mid-campaign.
Why organizers will love it
Email deliverability is invisible until it isn't: a magic link that never arrives, a registration confirmation sitting in spam, an open rate that craters because attendees don't recognize the sender. Every one of those used to start as a ticket and end with someone on our side interpreting DNS records for you — slow for you, and slower still when the fix was a single wrong character in a record.
Now the loop closes where the knowledge lives. The team that owns the domain manages the domain, sees the health of every record, and assigns senders across a whole community before the first campaign goes out. Faster setup, fewer tickets, and registration and marketing emails that land in the inbox your attendees are actually watching.
💡 Pro tip: Get your DNS contact in the room for the ten minutes it takes to publish the records. Verification is the only step that depends on someone outside the platform — everything after it is yours.
💡 Pro tip: For a recurring series, assign the sender address at community level rather than per event. Every future edition picks it up automatically, which kills the most common cause of an event going out from the default address.
