Use Your Mailgun Account in Customer.io

Overview

Using your Mailgun account in Customer.io is a practical move when you want tighter control over deliverability and sending reputation for revenue-critical flows like abandoned cart, browse abandon, post-purchase education, and winback. Instead of relying on a default sending setup, you connect Mailgun as your SMTP provider so your emails ride on the infrastructure you already trust and monitor.

A common D2C scenario is splitting risk: send high-volume promo campaigns on one stream, then protect cart recovery and transactional style messages (order updates, shipping, back-in-stock) with a separate Mailgun domain or subdomain to keep inbox placement stable when promotions spike.

If you want this wired cleanly across domains, subdomains, and message types without breaking reporting, Propel can implement the sending architecture inside Customer.io and help you pressure test it against your real flows. If you want help, book a strategy call.

How It Works

Using your Mailgun account in Customer.io works by routing email sends through Mailgun via SMTP credentials, while Customer.io still handles audience logic, personalization, and orchestration.

In practice, you set up a Mailgun sending domain (often a subdomain like mail.yourbrand.com), authenticate it (SPF, DKIM, and ideally DMARC), then add the Mailgun SMTP host, username, and password into your sending settings in Customer.io. Once connected, your campaigns and workflows send from the Mailgun-backed channel, and you can align different “From” addresses or domains to different message types.

For D2C, this is most valuable when you need predictable inboxing for flows that directly impact revenue within hours (cart recovery) and want to avoid deliverability swings caused by heavy promotional volume.

Step-by-Step Setup

Using your Mailgun account in Customer.io is straightforward, but the details matter if you care about attribution, inbox placement, and keeping flows stable during peak promos.

1. Create or confirm your Mailgun sending domain. Use a dedicated domain or subdomain for marketing email (for example, mail.yourbrand.com) so you can manage reputation separately from core corporate mail.
2. Authenticate the domain in Mailgun. Publish SPF and DKIM records, then add a DMARC policy (even a monitoring policy to start) so mailbox providers trust your domain.
3. Generate SMTP credentials in Mailgun. Use Mailgun’s SMTP user and password (do not reuse a shared credential across too many systems if you can avoid it).
4. Add Mailgun as your SMTP provider in Customer.io. Enter the Mailgun SMTP host, port, username, and password in your email sending settings.
5. Set your default “From” identity intentionally. Match the “From” domain to the authenticated domain in Mailgun, and keep naming consistent across flows (for example, “YourBrand” for promos, “YourBrand Orders” for order and shipping messages).
6. Send internal seed tests. Test to Gmail and Outlook inboxes, not just your own domain. Confirm headers show the expected authenticated domain and that links and images render correctly.
7. Roll out by message type. Start with a low-risk flow (welcome series), then move cart recovery and post-purchase, then finally high-volume promos once you see stable delivery.

When Should You Use This Feature

Using your Mailgun account in Customer.io makes the most sense when deliverability is a lever you actively manage, not something you hope stays fine.

• You run high-volume promotional sends. Mailgun gives you more control over reputation management so promos do not accidentally tank cart recovery performance.
• Your abandoned cart revenue is meaningful. If a 1 to 2 percent swing in inbox placement changes daily revenue, you want a sending setup you can monitor closely.
• You want separation between message classes. Many brands protect post-purchase and operational messages by using distinct domains or subdomains and consistent “From” identities.
• You need cleaner troubleshooting. When a flow underperforms, being able to isolate sending infrastructure from orchestration logic speeds up diagnosis.
• You are scaling internationally. As list size grows and engagement varies by region, having a robust sending provider helps maintain consistency.

Operational Considerations

Using your Mailgun account in Customer.io touches more than a credential field, it changes how you should think about segmentation, orchestration, and measurement.

• Segment by engagement to protect reputation. Route unengaged audiences into slower cadences or re-permissioning flows, and keep your high-intent segments (cart, browse, back-in-stock) prioritized.
• Align domains with customer expectations. If your order updates come from one identity and promos from another, keep the naming consistent so customers recognize you and engagement stays high.
• Make UTM governance part of the rollout. Ensure every email type uses consistent UTMs so you can compare cart recovery versus browse abandon versus winback without messy attribution.
• Plan for suppression and compliance. Confirm how unsubscribes, bounces, and complaints are handled end-to-end so you do not accidentally keep mailing suppressed customers.
• Warm up thoughtfully. If you introduce a new domain, ramp volume gradually starting with your most engaged customers, then expand outward.

Implementation Checklist

Using your Mailgun account in Customer.io goes live cleanly when you treat it like a deliverability project, not just an integration task.

• Mailgun sending domain or subdomain created and verified
• SPF and DKIM published and passing
• DMARC policy published (at least monitoring)
• SMTP credentials generated and stored securely
• Mailgun SMTP settings added in Customer.io and test sends confirmed
• Default “From” name and address standardized across flows
• UTM conventions applied across all templates
• Seed list tests completed for Gmail and Outlook inboxes
• Initial ramp plan defined (welcome, then cart, then post-purchase, then promos)
• Monitoring plan in place (bounce rate, complaint rate, inbox placement proxies)

Expert Implementation Tips

Using your Mailgun account in Customer.io pays off most when you pair the sending setup with smart audience pressure control.

• In retention programs we’ve implemented for D2C brands, the biggest win comes from protecting cart recovery and post-purchase messages with a more conservative sending posture (engaged-first targeting, tighter frequency), even when promo volume ramps hard.
• Keep winback flows on a separate cadence and consider a distinct subdomain if your list has a large inactive cohort. It reduces the chance that reactivation attempts drag down overall reputation.
• Use “reply-to” strategically. For high-intent flows like cart recovery, a monitored reply-to can surface real objections (shipping cost, sizing questions) that you can feed back into creative and offers.
• Do not change domains and templates at the same time. If performance drops, you want to know whether it was deliverability or creative.

Common Mistakes to Avoid

Using your Mailgun account in Customer.io can backfire when teams rush the setup or treat deliverability as a one-time checkbox.

• Launching on a fresh domain at full volume. New domains need warming. Going big immediately often lands you in spam, especially for promos.
• Mixing operational and promotional identity. If customers cannot tell what an email is, engagement drops and deliverability follows.
• Ignoring inactive segments. Sending heavy volume to unengaged customers is one of the fastest ways to degrade reputation, even with a strong provider.
• Inconsistent UTMs and link tracking. You end up “fixing deliverability” when the real issue is broken attribution or mismatched reporting.
• No rollback plan. Always know how you will revert or pause if bounce or complaint rates spike after switching providers.

Summary

Using your Mailgun account in Customer.io is the right call when email revenue depends on stable deliverability and you want more control over sending reputation. Prioritize it if cart recovery, post-purchase, and winback performance needs to stay reliable while promo volume scales.

Implement with Propel

Propel can connect Mailgun to Customer.io, set up domain strategy, and harden your flows so deliverability supports revenue, not volatility. book a strategy call.