Customer.io

Why behaviour-triggered email matters

Most email strategies treat customers as segments on a list. You send everyone in the "active users" segment a campaign about a new feature, and you hope it lands at the right time. But what if someone just signed up yesterday? They probably don't care about advanced features yet. What if someone upgraded last week? They're already bought in.

This is where behaviour-triggered messaging changes the game. Instead of broadcasting to a segment, you send a message at the exact moment a customer does something meaningful. When someone abandons their cart, you send a reminder immediately. When they complete onboarding, you send next steps. When they haven't logged in for 60 days, you send a win-back offer. The timing is contextual, not arbitrary.

The rise of customer data platforms

Customer.io sits in a category called customer data platforms (CDPs), though it's a lightweight version compared to enterprise platforms like Segment or mParticle. The idea is simple: collect events from your product, audience, and transactions, then use that data to personalise every interaction. Customer.io focuses on the messaging layer—email and SMS—rather than being a full data warehouse. This makes it more accessible for mid-market companies.

How Customer.io actually works

You connect your product to Customer.io via an API or pre-built integration (Shopify, Webflow, etc.). Every time a customer does something—signs up, views a product, makes a purchase—you send an event to the platform. Customer.io stores this event against the customer's profile. You then set up "journeys" or "automations" that listen for specific events. When a customer triggers an event that matches a rule, the platform sends a message (email or SMS) immediately or after a delay you specify.

For example: "When user_purchased event is received, send Template X after 1 hour." The platform will automatically send that email to every customer who purchases, at the exact right time.

What makes it different from other email platforms

Brevo and similar tools are broadcast-focused. You segment your list, create a campaign, schedule it for Tuesday at 2pm, and hit send. The timing is static. Customer.io is event-focused. Every message is triggered by something a customer did, so the timing is dynamic and contextual. This is why it's better for SaaS and product-driven companies; less useful for newsletter publishers or B2B agencies doing one-off campaigns.

Real-world use cases

SaaS onboarding: Send a welcome email immediately after signup, a "getting started" guide 24 hours later, a feature tour after they've logged in twice, and a "scheduling a demo" offer if they haven't upgraded after 7 days. Each message is triggered by real user behaviour, not guesswork.

E-commerce recovery: Someone adds items to their cart but doesn't check out. Within 2 hours, send an abandoned cart reminder. If they still don't buy, send a discount offer 24 hours later. If they do buy, send an order confirmation, then a "reorder soon" message after 30 days.

Community retention: A user hasn't logged into your community in 60 days. Trigger a "we miss you" message with highlights of recent activity. If they still don't return in another 14 days, send a final "last chance" message.

Pricing and integrations

Customer.io charges per contact, typically £0.01–0.03 per contact per month, depending on volume. No setup fees, no per-email charges. You pay for the size of your audience, not how many emails you send. This differs from platforms like Brevo, which often charge per send. Integrations include Shopify, WordPress, Zapier, and most standard webhooks. They offer a free tier for up to 500 contacts, with paid plans starting around £25/month.

Strengths and weaknesses

Strengths: Excellent for product-driven teams. Event-based logic is intuitive and powerful. Strong email deliverability. Good for mid-market SaaS. Simpler than enterprise CDPs.

Weaknesses: Limited SMS support compared to Twilio. Less powerful segmentation than Klaviyo if you need lots of conditional logic. No built-in landing pages. Customer support can be slow during peak times.

Who should avoid it

If you're sending a newsletter, Customer.io is overkill—use Substack or Beehiiv. If you need advanced segmentation or funnel analysis, Klaviyo (for e-commerce) or HubSpot (for B2B) are better. If you're not tracking user events in your product, you'll struggle to get value from the event-based model.

Verdict

Customer.io is the right choice if you have a product, clear user events, and you want messages to react to what customers actually do. The learning curve is moderate, but the payoff in engagement is worth it for SaaS and e-commerce teams. Most teams see a 2–3x lift in email engagement after moving to event-based triggers, because the messages are finally relevant.

What it does

Customer.io is a customer data and messaging platform. You create a behaviour map of your customers, when they sign up, upgrade, purchase, or hit any event you define, then automatically send messages triggered by those behaviours. Unlike email platforms that focus on list building and campaigns, Customer.io focuses on individual customer journeys. You feed in your user events, build segments, and automate personalised messages at scale.

How it works differently

Most email tools ask you to build campaigns and hope the right people are on the list. Customer.io inverts that: you send a customer event (e.g., "user_purchased"), and the platform matches it against automation rules you've set up. If the rule says "send a thank-you email to anyone who purchased in the last hour", the message goes out immediately. No manual campaign launching, no timing games. The platform sits between your product and your messaging, which means you can be far more granular about when people get messages.

Best for

SaaS companies with product-driven onboarding, e-commerce stores managing post-purchase flows, or any team with clear user events to trigger off. If your customer journey is predictable, sign up, confirm email, try feature, upgrade, Customer.io becomes very powerful. Less useful if you're doing mostly broadcast campaigns or if your user events aren't well-tracked in your product.

Pricing and learning curve

Customer.io charges per contact. A typical SaaS might pay £100 to 500/month depending on subscriber count. The learning curve is moderate, you need to understand event tracking in your product and be comfortable mapping behaviours to email triggers. Most teams get basic onboarding workflows live within a week, but sophisticated multi-step automations take longer.

Customer.io is a behavioural messaging and marketing-automation platform that triggers email, SMS, push, in-app, and WhatsApp messages from real-time user events and data. It is aimed at product, lifecycle, and growth teams at B2B SaaS and consumer companies that want event-driven rather than list-based campaigns. Pricing starts at 100 USD/month with no free plan, though a startup programme offers 12 months free for eligible early-stage companies.

As a B2B growth lead evaluating Customer.io, I approached this as a research-driven review (drawing on client feedback, documentation, and user reports) rather than personal product use. What I found is a platform with a strong reputation among data-savvy teams, but also some caveats for less technical marketers. Below I’ll outline the key strengths and weaknesses I’ve identified, and how Customer.io compares to other marketing automation tools in the B2B space.

Strengths

Customer.io’s greatest strength is its flexibility and power in automation. It’s hard to overstate how custom you can get with this tool: you can trigger messages off nearly any user event, use complex logic in workflows, and personalize content down to the individual level with data attributes. Unlike many email tools that focus only on newsletters or basic drip campaigns, Customer.io truly enables lifecycle marketing from onboarding flows to re-engagement, all automated based on real-time user behavior. Another big plus is the multi-channel capability: it’s not just email, but also push notifications, SMS (via Twilio), in-app messages, and even Slack or webhook actions in one unified workflow. This is ideal for product-led growth strategies where you might combine email with in-app nudges. Finally, for teams that have outgrown simple email platforms, Customer.io offers advanced segmentation and personalization (thanks to its data model and Liquid templating). Marketers with the right technical support can build extremely targeted campaigns that would be hard to achieve in more basic tools. In essence, the platform is a marketer’s toolkit for sophisticated, event-driven engagement, which is a strong advantage if that’s what your growth model needs.

Weaknesses

The flip side of that power is complexity. Customer.io is not the most intuitive platform, especially for newcomers. The UI, while functional, can feel a bit dated or cluttered in places, and some features are hidden behind technical setup. For example, achieving certain advanced personalization might require writing Liquid code in your emails not something every marketer is comfortable with. There’s consensus that the learning curve is steep. Small marketing teams without an engineer may struggle initially to get data flowing and campaigns running. Additionally, Customer.io lacks a few conveniences that broader marketing suites have. There’s no native landing page builder or form tool you’ll need external forms and then send the data via API or integration. Reporting and analytics are serviceable but not a strong point; deeper analysis often requires exporting data to external BI tools. Another consideration is support: standard support is mainly email and community forums, and some users note that response times can be slow. Priority support and onboarding assistance come only with the higher-cost plans. So, while the platform’s capabilities are top-tier, it demands more effort and technical involvement than many competing solutions. This isn’t a plug-and-play experience, and that’s the trade-off to be aware of.

Product and lifecycle teams at SaaS and consumer apps wanting behaviour-triggered, data-driven messaging across channels