Integrating with SendGrid comes with pros and cons, as well as some critical differences in how email is handled by Keela.
Read on to find out what happens after you integrate with SendGrid.
What does integrating with SendGrid mean?
The process of integrating with SendGrid involves setting up policies within your domain provider to point to another domain -- in this case, to SendGrid.
When you integrate with SendGrid and authenticate your domain, you are showing your email provider that SendGrid has your permission to send emails on your behalf.
Even though recipients of your emails may not notice much of a change, this can have a positive impact on your reputation as a sender and on your email deliverability.
Visit SendGrid to find out more about domain authentication.
What happens when I integrate with SendGrid?
When you integrate with SendGrid, Keela will allow you to choose to send emails from the following email addresses, depending on your settings:
- email@example.com for emails and e-blasts
- firstname.lastname@example.org for e-blasts
- email@example.com for emails and e-blasts (only if your login email is from the authenticated domain)
- firstname.lastname@example.org for e-blasts (organization-wide; optional)
If you choose to send emails from the custom domain (e.g. domain.org), SendGrid will send those messages directly on your behalf, and recipients will no longer see via keela.co on emails sent through Keela.
Note that when messages are sent using keela.co email addresses, if there are any errors during the sending process or on delivery, we can typically see what the problem was and help resolve the issue.
With SendGrid, since email is no longer routed through Keela (via keela.co), if there are issues with email deliverability, our Support team may not have access to information to help troubleshoot email issues. That means we may need to communicate with your IT department, technology or website administrator in order to resolve those issues, if any should occur.