Send Customer.io mail through your SMTP server
By default, Customer.io takes care of your email delivery. However, you can tell Customer.io to send mail through any other SMTP server.
Upsides to doing this
- You’re in full control.
- We won’t charge you anything based on the volume of email you send. You’ll only pay the plan cost based on the number of profiles in your account.
- We’ll still handle your open and click tracking.
- We’ll keep a full copy of your sent emails associated with the recipient.
Downsides to doing this
- Customer.io won’t have a feedback loop for data from the sending ESP.
- Data about delivered, bounced and spammed emails won’t be visible in Customer.io. We have integrations providing delivered, spam and bounce data with Mandrill, Mailgun, and Sendgrid
Configure custom SMTP settings
- Head to Email & Actions for your selected workspace
- Click the Add Custom SMTP Settings button, and then fill out the form:
When you save these settings, we’ll start sending emails through your own SMTP account.
Your port cannot be 25, 465, or 587; most major providers also allow delivery using port 2525 (like in our screenshot above). If you need alternatives, the best thing to do is consult your delivery provider’s documentation for ports that work with their service.
If you enabled custom SMTP, you are no longer required to complete the authentication process. The SPF and DKIM records need to be set up for your chosen STMP. Inside Customer.io, you only need to validate the domain ownership and the CNAME record if you want the tracking links to be branded using your domain rather than customeriomail.com.
If your Customer.io subscription is at the Startup level or higher you can add additional SMTP servers to segment deliveries by campaign type. For more details check out our documentation on configuring multiple SMTP accounts.
If you have any questions about setting this up, get in touch!