Eventleash sends invitations from your own domain, not from a generic address: what people see in their inbox is events@yourbrand.com, not a sender they do not recognise. For that to work you have to prove, once, that the domain is yours, by adding a few records to your DNS panel.
It is the only technical step of the whole setup. It takes five minutes — plus, if someone else runs your DNS, one email to them with the records to add.
Before you start
- The Admin role on the Eventleash account: the other roles do not see the domains section.
- Access to the DNS panel of the domain. Usually that is wherever the domain was registered (GoDaddy, Cloudflare, Namecheap, OVH, Aruba) or the panel of whoever runs your website.
- One decision: which address invitations should come from. You can use your main domain (
yourbrand.com) or a subdomain dedicated to events (events.yourbrand.com).
Adding the domain
- Open your user menu, top right, go to Account settings and then to the Domains section.
- Click Add domain.
- Type the domain with no
http://and nowww:yourbrand.comorevents.yourbrand.com. - Choose what it is for, with the two switches. You can turn both on for the same domain.
- Click Add domain: the next screen shows you the DNS records to copy.
| Switch | What it does |
|---|---|
| Use for sending | Send invitations, reminders and confirmations from this domain |
| Use for landing pages | Serve the public RSVP and sign-up pages on this domain |
The DNS records to add
You will always find them on the domain's row, in the Domains section, under DNS records. Clicking a cell copies it to the clipboard: the DKIM values are very long strings, and that is the safest way not to get one wrong.
Which records you need depends on what you turned on.
Ownership — always, one TXT record
It proves the domain is yours. It is the one record required in every case, for sending as much as for landing pages.
| Type | Name | Value |
|---|---|---|
TXT | _eventleash.yourbrand.com | eventleash-verification=<your key> |
The key is unique to your account. If the same domain has already been verified by another Eventleash account — which happens to agencies working on their clients' domains — it does not count as verified for you until you publish your own record.
The record lives on a label of its own (_eventleash.) rather than on the domain, so that it can coexist with the landing pages CNAME, which on its own would tolerate no other record beside it.
Sending — three CNAME records
These are the DKIM keys we sign with the mail we send on your behalf. They all look like this:
| Type | Name | Value |
|---|---|---|
CNAME | <token>._domainkey | <token>.dkim.amazonses.com |
The three tokens are generated by us and are different for every domain: copy them from the table in the app, not from this page.
Landing pages — one CNAME record
It points the subdomain at our public pages.
| Type | Name | Value |
|---|---|---|
CNAME | events.yourbrand.com | public.eventleash.com |
Checking that it worked
Once the records are saved in your DNS panel, go back to Domains and click Check status.
DNS is not instant: a few minutes is typical, but your provider may quote propagation times of up to 24 hours. If nothing changes on the first attempt you have not done anything wrong — try again later.
| Status | What it means |
|---|---|
| Pending | We are still waiting for the records. This is the normal state until DNS has propagated. |
| Active | All good: the domain can be used. |
| Failed | Verification was rejected. Check the records and retry from the same screen. |
Ownership is verified once: as soon as the TXT record is read, the domain stays verified for your account even if that record later disappears. The DKIM records, on the other hand, have to stay published forever, because they sign every single message.
Choosing the primary domain
The primary domain is the one campaigns go out from. Until you have one, the account is not ready to send: you can create events, contacts and campaigns, but not deliver them.
Only a domain with sending enabled and in the Active state can become primary. When there is one, a Set as primary button appears on its row.
The subdomain managed by Eventleash
When the account is created you already have one domain labelled Managed by Eventleash. It is a subdomain of ours, assigned to you, there to make landing pages work from day one: it needs no DNS record and cannot be removed.
It is not a sending domain though, and it does not replace yours: to send invitations you still have to connect a domain of your own.
SPF and DMARC
Everybody asks, and the answer is simpler than expected: you do not need to touch your SPF record.
Messages are DKIM signed with keys published on your domain, and it is that signature that aligns the message with your domain as far as DMARC is concerned. If you already have a DMARC policy, a strict one included, it keeps working with no change once the DKIM records are active.
If your IT people ask you to add an include: to your SPF for Eventleash, you can tell them it is not needed.
When something does not work
| Symptom | What to check |
|---|---|
| The status stays Pending for hours | That the records are on the right domain. Many panels append the domain to whatever you type: enter _eventleash.yourbrand.com and you may end up with _eventleash.yourbrand.com.yourbrand.com. In that case the name field takes just _eventleash. |
| The status stays Pending and the record is there | That the value carries no quotes or spaces added by the panel, and that there is only one TXT record with that name. |
| Verification comes back Failed | Retry with the button on the domain's row. If it keeps failing, write to us with the domain. |
| The DKIM records do not appear | Click Check status: they are generated when the domain is first registered with our mail provider. |
| The domain is Active but I cannot send | Check that you set it as primary, and that the account is not suspended over a payment problem. |
If you are still stuck after all this, write to [info@eventleash.com](mailto:info@eventleash.com) with the domain: from our side we can see exactly which record is missing.