When sending emails for your events in Swapcard, it's important to know how the platform handles email sending domains based on your plan—and how to send from your own domain for the best deliverability and branding. This guide covers both.
💎 This feature is a paid add-on.
Set up and verify your sender domains yourself
You no longer need to raise a support request to send from your own domain. With the Email Domain Manager in Studio, you can add a domain, publish the DNS records we generate for you, and watch each one verify in real time as your changes propagate. Once a domain is verified, you can create branded sender addresses and assign them to your events, all on your own.
Domains are added, verified, and managed in Organization Settings, so this sits with your organization's owners. It's also where you'll find each record's health and the View DNS details for any domain.
1. Add your domain
In your Organization Settings, open the Email Domain section and add the domain you want to send emails from (for example, yourdomain.com). Studio instantly generates every DNS record you need to publish:
2. Publish and track your records
Add the generated records in your domain's DNS management console, then follow their progress right inside Studio. Each record is checked on its own and shows one of three statuses:
Under verification – the record has been detected and is being validated.
Verified – the record is correctly configured and active.
Invalid – the record is missing or incorrect and needs attention.
An invalid record is flagged right in the same screen where you'd correct it, so you never have to open a support thread to find out why a magic link didn't arrive. Statuses refresh in real time as your DNS changes take effect, your IT contact publishes a record, you refresh, and the status moves, so you're never left guessing or waiting on a ticket.
Pro tip: Get your DNS contact in the room for the few minutes it takes to publish the records. Verification is the only step that depends on someone outside the platform, everything after it is yours.
3. Create your sender addresses
Once your domain shows as verified, create the sender addresses your attendees will see, such as hello@yourdomain.com, registration@yourdomain.com, or support@yourdomain.com.
4. Assign addresses to your events
Decide which events and communities can use each address:
Event and Community Managers then pick the address from the dropdown in their own settings, under Emails > Sender address.
Removing an address is safe: any event that was using it simply falls back to Swapcard's default sender address, so your communications never break mid-campaign.
Managing several organizations? You only need to verify a domain once. Enterprises running several organizations under one umbrella don't re-verify the same domain for each one, a verified domain can be shared across the group, so every team sends from the same authenticated domain without repeating the setup.
💡 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 prevents the most common cause of an event going out from the default address.
Good to know
Verification needs your DNS provider. Publishing the records is the only step that depends on someone outside the platform; everything before and after is managed in Studio.
Removing an address is safe. Any event using a deleted address falls back to the default sender, so communications never break mid-campaign.
Pair it with DMARC. For the strongest protection and deliverability, set up a DMARC policy for your domain too. See How to Configure DMARC Records for Your Domain.
Understanding how Swapcard handles email sending domains based on your plan ensures your event emails are delivered effectively. By using a custom domain and managing email server IPs, you can improve your email deliverability and enhance your event's professional image.