01What is DKIM?
DomainKeys Identified Mail (DKIM) is an email-authentication method. The sending system adds a digital signature to an email. The receiving mail system uses a public key available through DNS to check that the signature is valid and that the signed content has not changed in a way that invalidates it. DKIM identifies the signing domain; it does not verify the identity of the individual who wrote the email. Source: RFC 6376, §§1, 1.2 and 1.5
For Cvent’s request-based implementation, Cvent provides two CNAME records for your IT team to publish in your organization’s external-facing DNS. Cvent then validates the records and completes implementation. Cvent holds the corresponding private signing keys. Publishing the DNS records alone does not complete the process. Sources: DKIM Request Form; What is DKIM? → The DKIM Process
02Why implement DKIM?
Aligned DKIM gives receiving mail systems a way to authenticate Cvent messages against your sending domain and can provide a path to DMARC compliance. This matters when legitimate event communications might otherwise be quarantined or rejected because authentication and alignment do not meet the applicable policy. Source: RFC 7489, §§3.1, 6.3 and 6.7
DKIM is not a guarantee of inbox placement and does not resolve every bounce or delivery problem. Invalid addresses, recipient filtering, sender reputation, and other delivery conditions still require separate investigation. Sources: What is DKIM? → What’s next?; Implementing DKIM in Your Account → Understanding Undeliverable and Bounced Emails
03When is DKIM required or recommended?
| Situation | Requirement or recommendation | Action |
|---|---|---|
| Your organization sends Cvent emails using its own domain. | Cvent recommends DKIM as an initial authentication step. This is not evidence that every account must complete custom DKIM before sending any email. DKIM Request Form | Arrange setup and validation before relying on the domain for important event communications. |
| Messages must pass DMARC, and aligned SPF is not available or is not passing. | A passing, aligned DKIM signature is needed to provide the alternative DMARC pass path. DMARC itself does not require DKIM if aligned SPF already passes. RFC 7489, §§3.1 and 4.1 | Ask IT and Cvent Support to confirm the authentication path for the affected messages. |
Your domain has a DMARC policy of p=quarantine or p=reject. | Messages that fail DMARC can be quarantined or rejected under that policy. The policy does not make DKIM the only possible pass path. RFC 7489, §§6.3 and 6.7 | Validate alignment before production sending or stricter policy enforcement. |
| Your organization qualifies as a bulk sender to personal Gmail accounts. | Google requires SPF, DKIM and DMARC, plus From-domain alignment with SPF or DKIM. Its FAQ describes bulk senders as sending close to 5,000 messages or more in 24 hours, counted across the same primary domain. Google → Bulk senders and Email authentication | Have IT assess organization-wide volume—not just one event—and review all applicable sender requirements. |
| Your volume is below Gmail’s bulk threshold. | Google’s baseline authentication requirement is SPF or DKIM; it does not make both mandatory for every sender. Google → Email authentication requirements & guidelines | Do not assume DKIM is unnecessary: organizational policy and recipient requirements may still call for it. |
| You introduce another From domain or subdomain. | Cvent documents DKIM setup at the domain/subdomain level. What is DKIM? → Benefits of Aligned DKIM Signing | Ask Cvent whether additional setup is needed before using it. |
The Gmail example is not a complete checklist for all mailbox providers. IT should review the requirements of the providers relevant to your recipients. Other sender requirements, such as spam controls and applicable unsubscribe mechanisms, remain outside this DKIM setup procedure. Source: Google → Sender requirements and guidelines
04Before submitting the request
Cvent user or account administrator
- Identify every domain or subdomain used in the visible From address. Submit the domain portion, not a full email address.
- Confirm the correct Cvent account ID and the account’s US or EU environment.
- Identify the IT contact authorized to publish external DNS records.
- Tell IT which Cvent communications and sending domains need testing.
IT/DNS administrator
- Confirm that the organization owns or manages each requested domain/subdomain.
- Confirm that it exists and is configured for email use. Cvent’s implementation guidance requires MX records connected to a monitored, accessible inbox for replies and planner-address verification. This is a Cvent setup prerequisite, not a universal requirement of the DKIM protocol.
- Review the domain’s DMARC policy and alignment settings.
- Request 2048-bit RSA DKIM keys where supported. Cvent documents 2048-bit keys as available on request; RFC 8301 recommends RSA keys of at least 2048 bits. Confirm the actual configuration with Cvent rather than relying on a default.
Sources: Implementing DKIM in Your Account → Configuring Domains and Subdomains; What is DKIM? → Benefits of Aligned DKIM Signing; RFC 8301, §3.2.
05Submit the DKIM request
The following navigation and field labels are taken from the supplied MPI document. The request URL is corroborated by Cvent guidance, but the live form’s later pages and exact labels were not independently verified. Follow the current form if its layout differs.
- Open the DKIM Request Form.
- Select “Complete form,” if displayed.
- Enter your first name, last name, and email address, then select “Next.”
- Complete the account and domain details below.
- Review and submit the request. Retain the confirmation and any case reference supplied.
| Field | What to enter |
|---|---|
| Cvent Account ID | The supplied MPI guide lists MPIFOUN001. Confirm this with the MPI account administrator before submission; it has not been independently verified. |
| Email Domain | Every domain/subdomain you intend to use for Cvent sending. The supplied guide instructs users to separate multiple domains with commas; follow the current form’s instructions. |
| Region / Login Page URL | The environment in which the Cvent account is hosted: US or EU. Confirm with the account administrator or Cvent Support. Do not select a region solely from your physical location or the event location. |
Cvent’s form states that implementation is domain-specific, not account-specific, and asks users to include all relevant domains. Still provide the account and environment information requested so Cvent can identify the correct context. Source: DKIM Request Form
Request-form reference screens
These screenshots are reproduced from the supplied MPI guide. They are reference images, not confirmation of the live form’s current appearance.
06Complete DNS setup and activation
| Step | Owner | Action |
|---|---|---|
| 1. Obtain records | Cvent Support | Cvent provides the two CNAME records for the requested domain. |
| 2. Publish records | IT/DNS administrator | Publish the exact record names and targets supplied by Cvent in external-facing DNS. Do not generate or guess replacement values. |
| 3. Notify Cvent | Request owner | Tell the specialist handling the request when the records have been published. |
| 4. Validate and complete | Cvent Support | Cvent validates the records and completes implementation. Obtain confirmation before treating setup as complete. |
| 5. Test messages | Request owner and IT | Send test emails and validate the authentication results. |
Please note: in case of any questions please reach out to Cvent System administrators
