How to Set Up DKIM for Cvent

Cvent sends critical emails on your behalf every day: event invitations, registration confirmations, schedule reminders, and post-event surveys. If those emails land in spam folders instead of inboxes, your event attendance suffers directly. Setting up DKIM (DomainKeys Identified Mail) authentication for Cvent ensures receiving mail servers can verify your event emails are legitimate and authorized by your domain.

Why DKIM Matters for Cvent

Event emails are uniquely time-sensitive. A marketing email that arrives a day late is an inconvenience. An event invitation that arrives in spam means an empty seat. A last-minute schedule change that gets filtered means a confused attendee.

Without DKIM, receiving servers have no way to verify that Cvent's emails are actually authorized by your domain. They see a message claiming to be from events@yourdomain.com but sent from Cvent's infrastructure, and they treat it with suspicion. DKIM bridges that gap by cryptographically proving the message was authorized.

With DKIM properly configured, your Cvent emails pass authentication checks, reach inboxes more reliably, and build positive sender reputation for your domain over time.

Before You Start

You will need:

Cvent administrator access to your organization's account
DNS management access for the domain you use in your Cvent "From" address (through providers like Cloudflare, GoDaddy, Namecheap, etc.)
The exact domain you use as your sending address in Cvent

Make sure you know which domain Cvent sends from on your behalf. If your event emails come from events@yourcompany.com, the domain you need to configure is yourcompany.com.

Setting Up DKIM for Cvent

Log into Cvent admin

Sign into your Cvent account with administrator privileges. You need access to the organization-level settings, not just individual event management.

Navigate to email authentication settings

Go to Account Settings or Organization Settings and find the Email or Sender Authentication section. Depending on your Cvent product (Event Management, Marketing, or Webinar), the exact navigation path may differ.

Find or generate DKIM records

Select the option to authenticate a new domain or configure DKIM. Enter the domain you use in your "From" address. Cvent will generate DNS records for you, typically CNAME records that point to Cvent's DKIM infrastructure.

Add the records to your DNS

Log into your DNS provider and create new CNAME records using the values Cvent provided. The record typically looks like:

Type: CNAME
Host/Name: Something like cvent-dkim._domainkey (Cvent specifies this)
Value/Target: A Cvent hostname (e.g., dkim.cvent.com or a unique identifier)

Copy the values exactly as Cvent provides them. If your DNS provider automatically appends your domain, you may need to omit the domain suffix from the hostname.

Wait for propagation

DNS changes typically propagate within 15 to 60 minutes, though it can take up to 48 hours in some cases. Most providers update within an hour.

Verify in Cvent

Return to Cvent's email authentication settings and click Verify or Check Status. Cvent will query your DNS to confirm the records are in place. Once verified, Cvent begins signing your outbound emails with DKIM.

Adding DNS Records: CNAME vs TXT

One point that confuses many people is that Cvent uses CNAME records for DKIM rather than the TXT records you might expect. Both approaches are valid, but they work differently.

Record Type	How It Works	Key Management
TXT	Your DNS contains the actual DKIM public key directly	You manage key rotation manually
CNAME	Your DNS points to the provider's server, which serves the key	Provider rotates keys automatically

Cvent uses the CNAME approach because it allows them to rotate DKIM keys on your behalf without requiring you to update DNS each time. This is the recommended method. The important thing is to create a CNAME record, not a TXT record. If you put the Cvent hostname into a TXT record, DKIM will not work.

Verify Your Cvent DKIM Setup

After Cvent confirms verification, independently test the record using our free DKIM checker to make sure it resolves correctly from the public internet.

Look up [selector]._domainkey.yourdomain.com using the selector that Cvent provided. If the lookup returns a valid public key, your DNS configuration is correct.

Testing Your Setup

Once DKIM is verified, send a test event email through Cvent and check the results.

Create a test event or use an existing one

Set up a quick test event in Cvent, or use a draft event you already have.

Send a test invitation

Send an invitation to an email address you control, ideally a Gmail address, since Gmail makes it easy to inspect authentication results.

Check the email headers

Open the received email, click the three dots, and select Show original (in Gmail). Look for the Authentication-Results header and confirm you see dkim=pass with your domain.

Common Issues

Verification stays pending: DNS changes may not have propagated yet. Wait at least 30 minutes before retrying. Double-check that you created CNAME records (not TXT or A records) and that the hostname is not duplicated (e.g., selector._domainkey.yourcompany.com.yourcompany.com).

DKIM check fails after initial verification: The CNAME record may have been deleted or overwritten. Verify it still exists in your DNS and that no conflicting records share the same hostname. Some DNS providers do not allow CNAME records alongside other record types for the same name.

Multiple sending domains: If you use different "From" domains for different events or divisions, you need to set up DKIM for each domain separately. Repeat the process for every domain that appears in your Cvent "From" addresses.

Cvent requires domain-level sending authorization

Cvent may require you to verify domain ownership before enabling custom DKIM signing. Make sure you complete any domain verification steps Cvent requires in addition to the DKIM DNS records. Check Cvent's current documentation for the latest requirements, as their interface and processes update periodically.

Complete Your Authentication

DKIM is one piece of a three-part email authentication strategy. For the best deliverability with your Cvent event emails, also set up:

SPF (Sender Policy Framework): Add Cvent's sending servers to your SPF record so receiving servers know Cvent is authorized to send on your behalf. Check your current SPF configuration at spfrecordcheck.com.

DMARC (Domain-based Message Authentication, Reporting and Conformance): Publish a DMARC policy that tells receiving servers what to do when authentication fails. Start with p=none to monitor, then move toward enforcement. Check your DMARC record at dmarcrecordchecker.com.

If you need to generate a custom DKIM key for any reason, dkimcreator.com can help you create one with the right key size and format.

Never miss a DKIM issue

Monitor your SPF, DKIM, DMARC and MX records daily. Get alerts when something breaks.

Start Monitoring