Summary
The consensus among experts, marketers, and official documentation is that you **absolutely need** separate DKIM records for each ESP (Email Service Provider) you use, such as HubSpot, Sendgrid, and ActiveCampaign. This is crucial for ensuring proper email authentication, preventing authentication conflicts, maximizing inbox placement, and avoiding spam filters. Each sending source, including Google Workspace, transactional emails, and marketing campaigns, should have its own DKIM signature. Failure to do so can negatively impact deliverability and damage your sender reputation.
Key findings
- Unique DKIM Required: Each ESP needs its own DKIM record for proper authentication and deliverability.
- Enhances Authentication: DKIM verifies the authenticity of emails and that the sender is authorized to send emails on behalf of a domain.
- Improves Deliverability: Correct DKIM configuration significantly improves email deliverability and inbox placement, preventing emails from being marked as spam.
- Prevents Conflicts: Using separate DKIM records prevents authentication conflicts between different ESPs.
- Maintains Reputation: Proper DKIM setup helps maintain a positive sender reputation for each domain or subdomain.
Key considerations
- ActiveCampaign Specifics: ActiveCampaign has custom DKIM records (2 CNAMEs instead of one), and custom return paths are primarily available for Enterprise plans.
- Google Workspace Setup: Ensure Google Workspace (or any other email source) is configured to sign DKIM; otherwise, emails from that source may not be properly authenticated.
- Record Alignment: Align SPF, DKIM, and DMARC records with the email's origination point to ensure end-to-end authentication.
- All Sending Sources: Remember to configure DKIM for all sources that send email on your behalf, including transactional emails, marketing campaigns, and direct emails from services like Google Workspace.
What email marketers say
11 marketer opinions
When using multiple Email Service Providers (ESPs) like HubSpot, Sendgrid, and ActiveCampaign, it's crucial to configure a unique DKIM record for each ESP. This ensures that each service can properly authenticate emails sent on your behalf, improving deliverability and preventing emails from being marked as spam. Failing to set up separate DKIM records can lead to authentication issues and a damaged sender reputation.
Key opinions
- Unique DKIM Required: Each ESP (e.g., HubSpot, Sendgrid, ActiveCampaign) requires its own dedicated DKIM record for proper email authentication.
- Improved Deliverability: Proper DKIM configuration for each ESP ensures better email deliverability and inbox placement.
- Prevents Authentication Issues: Using separate DKIM records prevents authentication conflicts between different sending services.
- Maintains Sender Reputation: Individual DKIM records help maintain a positive sender reputation for each domain or subdomain.
- Avoids Spam Filters: Correctly configured DKIM records help prevent emails from being flagged as spam.
Key considerations
- ActiveCampaign DKIM: ActiveCampaign utilizes custom DKIM records (2 CNAMEs instead of one), and custom return paths may only be available for Enterprise plans, though this might change.
- Domain Alignment: Ensure that SPF/DKIM/DMARC records align with the origination point of the email. If emails originate from different sources (e.g., Google Workspace and ActiveCampaign), each needs proper authentication.
- Ongoing Monitoring: Regularly monitor DKIM records and email deliverability to identify and address any potential issues.
- All Sending Sources: Each email service that sends mail on your behalf should be properly DKIM signed including transactional mail, marketing campaigns and direct mail from services like Google Workspace.
Marketer view
Email marketer from MailerLite explains that you should set up DKIM records for each ESP to properly authenticate your emails. This ensures that your emails are not marked as spam and improves your overall email deliverability.
3 May 2022 - MailerLite
Marketer view
Email marketer from Mailjet explains that it is essential to configure DKIM for each ESP you use. Each provider will give you its own DKIM record to add to your DNS to ensure proper authentication.
16 Dec 2021 - Mailjet
What the experts say
3 expert opinions
Experts emphasize the importance of configuring DKIM for each sending service, especially when using multiple ESPs like HubSpot, Sendgrid, and ActiveCampaign. Ensuring that each service has its own DKIM record is crucial for proper authentication, preventing conflicts, and guaranteeing emails are verified by recipient servers. If a service, like Google Workspace, isn't configured to sign DKIM, it can lead to deliverability issues.
Key opinions
- DKIM Signing Required: Each email sent should be DKIM signed.
- Unique DKIM for Each Service: Each sending source requires its own DKIM record to ensure emails are verified.
- Authentication Benefits: Proper DKIM configuration improves email authentication and helps avoid deliverability issues.
Key considerations
- Google Workspace Configuration: Verify that Google Workspace or any other email source is properly configured to sign DKIM.
- Troubleshooting: If DKIM isn't configured correctly, it can lead to deliverability problems; fixing it can improve email delivery.
- Conflict Prevention: Using individual DKIM records for each ESP prevents authentication conflicts between the different sending services.
Expert view
Expert from Email Geeks explains that DKIM requires each email sent to be signed. If Google Workspace isn’t configured to sign DKIM, then the email sent from there isn’t signed. He suggests fixing it to see what happens.
13 Sep 2022 - Email Geeks
Expert view
Expert from Spam Resource shares that each sending source should have its own DKIM record. This configuration prevents authentication conflicts and ensures each ESP’s emails are properly verified by recipient servers.
23 Nov 2021 - Spam Resource
What the documentation says
5 technical articles
Official documentation from various sources like SendGrid, Google Workspace, IETF, Microsoft, and AuthSMTP consistently states that when sending emails from multiple services or ESPs, each service should have its own DKIM key or record. This ensures proper authentication, improves deliverability, enhances email security, and prevents emails from being marked as spam.
Key findings
- Individual DKIM Keys: Each sending source/service (including ESPs and sending domains/subdomains) requires a separate and unique DKIM key or record.
- Enhanced Authentication: DKIM allows a domain to associate a signature with an email message, vouching for its authenticity.
- Improved Deliverability: Proper DKIM configuration enhances email security and ensures that your messages are trusted by recipient email servers, improving deliverability and reducing spam.
- Security Enhancement: Setting up DKIM enhances email security by ensuring messages are trusted and properly authenticated.
Key considerations
- Multiple Services: When using multiple services (like your own server and a marketing service), each service should use a separate DKIM record.
- Domain/Subdomain Specific: Each sending domain or subdomain should have its own DKIM record.
- Preventing Spam: Proper DKIM setup helps in avoiding spam filters and improving email deliverability.
Technical article
Documentation from SendGrid explains that if you send email from multiple services, each should have its own DKIM key. This ensures proper authentication and prevents deliverability issues.
25 Sep 2023 - SendGrid
Technical article
Documentation from Google Workspace Admin Help explains that each sending source (e.g., Google Workspace, marketing platform) should have its own DKIM signature to improve deliverability and avoid spam filters.
28 Jan 2024 - Google
Can I use the same sending domain with multiple ESPs?
Do SPF and DKIM records need to be aligned for all email service providers?
How do ActiveCampaign and other ESPs handle DMARC records during custom return-path setup, and what are the potential issues?
How do I configure DNS records to send emails from two different ESPs using the same subdomain?
How do I set up an SPF record when using multiple email sending services?
How do I set up SPF and DKIM records for new subdomains when using third-party email services?
How do SPF records and DKIM keys work with multiple email services like Klaviyo and Shopify?
How should I combine SPF records and what domain should I use with SendinBlue?
