Multiple Subscription Types in Customer.io

Overview

Multiple subscription types in Customer.io help you separate shopper preferences so a customer can unsubscribe from promos without losing order updates, back-in-stock alerts, or VIP drops. In a D2C program, this is the difference between preserving high-intent channels (transactional and replenishment) while still respecting a customer who is tired of weekly promotions.

Anonymous messaging in Customer.io often gets the spotlight, but subscription types are what keep your list healthy once the customer identifies and starts receiving more frequent messaging. Propel can help you map subscription types to your actual merchandising calendar and automate preference-aware journeys in Customer.io, if you want to book a strategy call.

How It Works

Multiple subscription types in Customer.io work by assigning each message to a specific subscription category, then honoring a person’s opt-in or opt-out status per category instead of treating “unsubscribe” as one global switch.

In practice, you define your subscription types (for example, Promotions, New Arrivals, Back-in-Stock, Replenishment Reminders, Order Updates). When you send an email from a campaign or workflow, you select the relevant subscription type. If a shopper unsubscribes from Promotions, they can still receive Order Updates and Back-in-Stock messages, assuming those categories remain subscribed and your sending settings support that behavior.

Once you have types in place, segmentation becomes cleaner. You can build audiences like “Subscribed to Back-in-Stock” or “Unsubscribed from Promotions but subscribed to New Arrivals” and route those people into different paths. This is especially useful when you are orchestrating multi-touch cart recovery and post-purchase flows in Customer.io.

Step-by-Step Setup

Multiple subscription types in Customer.io are easiest to set up when you start from your message inventory, not from the tool.

1. List your email programs and label them by intent (transactional, service, promotional, product discovery, replenishment, winback).
2. Convert that list into 4 to 8 subscription types that a shopper would actually understand (avoid internal labels like “Flow 7”).
3. Create the subscription types in your workspace settings (name, description, and any default behaviors your team needs).
4. Update every email campaign and workflow message to use the correct subscription type (promos should never share the same type as order updates).
5. Update your unsubscribe links and preference center experience so shoppers can opt down instead of only opting out (at minimum, offer “Promotions” separately from “Order Updates”).
6. Build segments for each subscription type status (subscribed, unsubscribed) and use them as entry filters or branches in key journeys like cart recovery and winback.
7. QA with test profiles by unsubscribing from one type and confirming other types still send as expected.

When Should You Use This Feature

Multiple subscription types in Customer.io are most valuable when you have more than one reason to email a customer, and you want to protect revenue-critical messages while reducing complaint risk.

• Cart recovery without list churn: If shoppers unsubscribe after heavy promo pressure, separate “Cart and Checkout Reminders” from “Weekly Promotions” so you can still recover near-term revenue while respecting promo fatigue.
• Post-purchase engagement that drives second order: Keep “Order Updates” and “Product Care” separate from “Cross-sell” so customers can opt out of upsells without losing service messages that reduce WISMO and protect deliverability.
• Back-in-stock and waitlist monetization: Make “Back-in-Stock” its own type so customers who only want that alert remain reachable even if they opt out of general marketing.
• Replenishment and subscription-like behavior: For consumables (coffee, skincare, supplements), a dedicated “Replenishment Reminders” type often outperforms promos because it is timing-based and expectation-aligned.
• VIP and early access programs: Create a “VIP Drops” type so your best customers can stay opted into high-value launches without receiving everything else.

Operational Considerations

Multiple subscription types in Customer.io only work when your data and orchestration stay consistent across channels and teams.

• Message taxonomy: Decide what counts as promotional versus service. For example, “Your order shipped” is service, but “Add this to your order before it ships” is promotional, even if it references an order.
• Preference capture: If you collect email on-site (popups, checkout, quiz), pass the intended opt-in scope. A quiz opt-in might reasonably map to “New Arrivals” rather than “All Promotions.”
• Event-driven flows: Cart, checkout, and browse events should route into journeys that check subscription status at send time, not only at entry time, since preferences can change mid-flow.
• Deliverability and complaint control: Subscription types reduce global unsubscribes, but they will not save you from over-sending. Keep frequency rules and suppression logic in place.
• Cross-tool alignment: If you also have Shopify email tools, loyalty platforms, or support tools sending email, align categories so “unsubscribed from promos” means the same thing everywhere.

Implementation Checklist

Multiple subscription types in Customer.io roll out cleanest when you treat it like a migration and not a quick toggle.

• Inventory every email and assign a subscription type
• Create 4 to 8 shopper-friendly subscription types with clear descriptions
• Update all campaign and workflow emails to the correct type
• Confirm transactional and service messages are not tied to promotional types
• Implement or update your preference center and unsubscribe experience
• Add subscription-status checks to cart recovery, post-purchase, and winback journeys
• QA unsubscribe scenarios across types using test profiles
• Document rules so new campaigns do not default to the wrong type

Expert Implementation Tips

Multiple subscription types in Customer.io become a revenue lever when you intentionally design opt-down paths, not just opt-out paths.

• In retention programs we’ve implemented for D2C brands, the highest impact setup is separating “Promotions” from “Back-in-Stock” and “Replenishment.” Those two categories often have the highest click-to-purchase intent and the lowest complaint rates.
• Build a “promo fatigue” branch: if a customer clicks unsubscribe from Promotions, offer a one-click downgrade to “Monthly Highlights” instead of losing them entirely.
• For cart recovery, keep the subscription type consistent across the series. Mixing types inside the same recovery flow creates confusing behavior when a shopper opts out mid-series.
• Use subscription status as a segmentation input for creative. Someone unsubscribed from Promotions but subscribed to New Arrivals should get product-led discovery messaging, not discount-led messaging.

Common Mistakes to Avoid

Multiple subscription types in Customer.io can backfire when teams treat categories as internal folders instead of real customer preferences.

• Too many types: If you create 15 categories, your preference center becomes unusable and shoppers choose the nuclear option (unsubscribe).
• Misclassifying service as promo: Putting order updates under Promotions increases support volume and damages trust.
• Forgetting to assign types to messages: New campaigns often default to the wrong type unless you enforce a QA step.
• Only checking preferences at journey entry: If someone unsubscribes after the first cart email, the next sends should respect the new status.
• No measurement plan: Track unsubscribe rate by subscription type so you know which program is causing churn.

Summary

Use multiple subscription types when you want shoppers to opt down instead of opting out, while protecting high-intent messages like back-in-stock and replenishment. It is one of the simplest ways to improve deliverability and preserve repeat purchase revenue in Customer.io.

Implement with Propel

Propel can help you design subscription types that match how your customers shop, then wire them into cart recovery, post-purchase, and winback journeys in Customer.io. If you want help scoping and implementing it end-to-end, book a strategy call.