Customer.io
How to use 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.
Read the full guideShow less
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.
How to automate Customer.io
API and webhooks
Customer.io has a documented API and webhooks at docs.customer.io. Send events from your app on signup, upgrade and key feature use, and use webhook actions in a workflow to notify your team chat or call your own service.
MCP server
Customer.io has an official MCP server, included on all plans, with getting-started docs at docs.customer.io/ai/mcp. Connect an assistant to ask which campaigns have the lowest conversion this month. Check the getting-started docs for the endpoint URL.
Built-in automation
Campaigns and workflows are the core automation. Build one for onboarding: signup starts it, the user's activity decides which message follows, and people who reach the key feature leave the flow.
I did not find confirmation of a Zapier or Make app on the vendor's site, so check before you plan around one.