Use Your Mailjet Account in Customer.io

Overview

Using your Mailjet account in Customer.io is most valuable when you want tighter control over deliverability, branding, and sending reputation while scaling revenue flows like abandoned cart, post-purchase cross-sell, and reactivation. Instead of treating email as a generic channel, you can align sender identity, authentication, and IP strategy with how your store actually sells.

If you want this wired cleanly across events, segmentation, and creative QA without slowing down your team, Propel can implement it end to end inside Customer.io. If you want help pressure testing your deliverability and flow plan, book a strategy call.

How It Works

Using your Mailjet account in Customer.io means Customer.io generates and queues the messages, but hands off the actual email delivery to Mailjet via your Mailjet SMTP credentials.

Operationally, your flows, triggers, and Liquid personalization still live in Customer.io, and Mailjet becomes the sending infrastructure that determines how mail is authenticated, routed, and throttled. You typically configure Mailjet as a custom SMTP provider, then choose it as the sender for campaigns and transactional messages where deliverability matters most.

This is especially helpful when you are splitting traffic, for example sending high-intent revenue messages (cart, browse abandonment, price drop) through the most protected sending path, while keeping lower stakes newsletters on a different path. For teams that need more hands-on deliverability control, we usually pair this with domain alignment and a clear suppression strategy inside Customer.io.

Step-by-Step Setup

Using your Mailjet account in Customer.io is straightforward, but the details matter if you care about inbox placement on high-revenue flows.

1. In Mailjet, confirm the sending domain you plan to use (the same domain your brand uses for customer communication, not a random subdomain unless you have a reason).
2. Set up domain authentication in Mailjet (SPF and DKIM). If you are migrating from another ESP, avoid leaving old SPF/DKIM records in a broken state.
3. In Mailjet, generate or locate your SMTP credentials (username and password) for the sending account.
4. In Customer.io, go to your email sending settings and add a custom SMTP provider.
5. Enter the Mailjet SMTP host, port, and your Mailjet SMTP credentials. Use the encryption option recommended by Mailjet for production sending.
6. Set the “From” name and “From” email defaults to match what customers already recognize from your brand.
7. Send test emails to multiple inbox providers (Gmail, Yahoo, Outlook) and verify headers show authentication passing.
8. Assign the Mailjet SMTP provider to the specific campaigns and transactional messages that drive revenue (cart recovery, checkout abandonment, shipping updates, replenishment reminders).
9. Turn on monitoring: watch bounces, blocks, spam complaints, and suppression growth during the first week after switching.

When Should You Use This Feature

Using your Mailjet account in Customer.io makes the most sense when email performance is being held back by sending reputation, authentication complexity, or the need to separate traffic types.

• You are scaling abandoned cart and browse abandonment: cart and checkout emails are often your highest ROI sends, so you want the most stable sending setup and consistent authentication.
• You need to separate marketing and transactional risk: if a promo-heavy calendar is hurting deliverability, routing transactional and high-intent revenue messages through a protected path can stabilize performance.
• You are migrating from another ESP: keeping Mailjet as the sending layer while rebuilding flows in Customer.io can reduce disruption during the transition.
• You want tighter deliverability tooling: some teams prefer Mailjet’s deliverability controls and reporting while using Customer.io for orchestration and segmentation.

Real D2C scenario: A skincare brand sees cart recovery drop after ramping up promotional sends. They keep newsletters on one provider, but route cart, checkout abandonment, and post-purchase education through Mailjet with stricter authentication and volume discipline. Revenue recovers without cutting promo volume as aggressively.

Operational Considerations

Using your Mailjet account in Customer.io affects more than a single setting, it changes how you should run segmentation, suppression, and QA.

• Suppression alignment: decide whether Customer.io suppression lists, Mailjet suppression, or both are your source of truth. In retention programs we’ve implemented for D2C brands, double suppression without a plan often causes “mystery” delivery gaps in cart recovery.
• Traffic shaping: separate high-intent flows from broadcast-heavy traffic. If you cannot separate infrastructure, at least separate sending windows and frequency rules so cart recovery is not competing with promos.
• Event timing and orchestration: make sure your checkout events are clean (started_checkout, added_to_cart, purchase) and deduped. SMTP changes do not fix noisy events, they just make the noise deliver better.
• Creative QA: test dark mode, mobile rendering, and link tracking parameters. A deliverability upgrade is wasted if your cart email breaks on iOS Mail.
• From-domain consistency: keep “From” domains consistent across flows so customers recognize you and mailbox providers build stable reputation signals.

Implementation Checklist

Using your Mailjet account in Customer.io goes smoothly when you treat it like a revenue-critical infrastructure change, not a quick toggle.

• Mailjet domain authenticated (SPF, DKIM) and verified
• SMTP credentials generated and stored securely
• Custom SMTP provider added in Customer.io with correct host, port, and encryption
• Test sends validated across Gmail, Yahoo, Outlook (authentication passing)
• Key flows assigned to Mailjet sender (cart, checkout, post-purchase, winback)
• Suppression strategy documented (where unsubscribes and bounces live)
• UTM and attribution parameters confirmed for all revenue messages
• Monitoring plan in place for bounce rate, spam complaints, and deliverability shifts

Expert Implementation Tips

Using your Mailjet account in Customer.io performs best when you design around deliverability realities and not just channel setup.

• Protect cart recovery with routing and rules: in retention programs we’ve implemented for D2C brands, the fastest win is isolating cart and checkout abandonment from the “promo blast” pattern. Even if you send both through Mailjet, use stricter frequency caps and avoid stacking sends in the same hour.
• Warm up intentionally if you change domains or IP posture: if you are moving from one sending domain to another, ramp volume based on engagement. Start with post-purchase and high-intent segments before broad promos.
• Use a branded subdomain when appropriate: for some brands, using something like email.brand.com for marketing mail helps keep root domain reputation cleaner. Do this only if you will maintain consistency long term.
• Audit header-level consistency: check that the visible From, the return-path, and authentication align. Misalignment can quietly hurt inbox placement even when messages “send.”

Common Mistakes to Avoid

Using your Mailjet account in Customer.io can backfire if you rush the switch or ignore the downstream effects on data and deliverability.

• Switching sending without validating authentication: teams often test “it arrived” but do not confirm SPF/DKIM pass consistently.
• Breaking unsubscribe expectations: if unsubscribes are not honored consistently across systems, complaint rates rise fast, especially on winback and promo-heavy segments.
• Routing everything through one path: mixing newsletters and high-intent cart recovery without frequency discipline can reduce revenue even if total sends increase.
• Ignoring bounce and block patterns: hard bounces and provider blocks are early warning signs. If they spike, pause promos before they contaminate your highest intent flows.
• Assuming SMTP fixes weak strategy: deliverability upgrades amplify what you already do. If your cart series is one email with no product context, you will not magically get better conversion.

Summary

Using your Mailjet account is a strong move when you need more control over deliverability and sender reputation for revenue-critical flows. Prioritize cart, checkout, and post-purchase messages first, then expand once performance is stable inside Customer.io.

Implement with Propel

Propel can connect Mailjet to Customer.io, validate authentication, and re-map your highest revenue flows so deliverability improvements translate into more recovered carts and repeat purchases. book a strategy call.