How to Connect Customer.io to Your App and Send One Triggered Email
Customer.io sends email, SMS, push and in-app messages triggered by events in your product. It has no free tier, pricing starts around $100/month, and profiles and sends are metered separately — so the goal of week one is one working flow, not ten.
What makes Customer.io different from a newsletter tool?
It expects events, not lists. You send invoice.paid, the tool filters on properties, and the campaign fires. Compare that with MailerLite or ConvertKit, where the model is subscribers and broadcasts.
That event model is why product-led SaaS teams pick it and why simple newsletters should not. If your sending is a weekly digest to one list, Customer.io is a $100/month answer to a $0 problem.
How do you connect the app?
- Create the workspace in Customer.io and copy the Track API key (write key) from Settings.
- Identify a person with their permanent ID and attributes — create a test profile first.
- Send one track event with properties.
- Confirm the event appears on the person’s timeline.
- Build the campaign on that event.
Step 2 must use a stable ID you control. If you use an email address as the person ID, the entire profile breaks when someone changes it — and people do.
// identify once on login
aio.identify(user.id, { email: user.email, plan: "team", created_at: user.createdAt });
// then track the event your campaign will trigger on
aio.track("invoice_paid", { invoice_id: inv.id, amount: inv.amount });
How do you build the first campaign?
Use a single trigger and a single message. Edit the campaign, set the trigger event to invoice_paid, add a filter (amount > 0), and pick email as the channel.
Keep these three settings explicit:
- Trigger frequency — once per person per event. Not repeatable.
- Quiet hours — set your sending window, or identical emails land at 3 a.m. in Europe.
- Suppression — exclude anyone who unsubscribed, bounced, or is on your internal list.
That last one is the difference between a working flow and a deliverability incident. Import your suppression list before the first send, and check fixing deliverability on a new domain if the domain is fresh.
What does the billing model change about how you build?
Everything about volume. Profiles and sends are metered separately, so a flow that re-triggers on every page view multiplies sends without touching your profile count. Budget for sends first.
Practical guardrails: cap campaigns at one send per person per 24 hours, and use attribute-based filters to exclude low-intent segments before the send is created, not after.
How do you verify the send actually happened?
Send to an internal seed address, then check three things in order: the person’s timeline shows the trigger event, the message appears as sent, and the seed inbox receives it from your configured sending domain, not a shared one.
If the timeline shows the event and the inbox is empty, the problem is deliverability or a suppression rule, not the campaign logic. Test in that order to avoid debugging the wrong layer.
Teams running Resend for transactional mail sometimes split duties — Resend for receipts, Customer.io for lifecycle messaging. That is a reasonable division but means maintaining two suppression logic paths.
When should you not use Customer.io?
Simple newsletters, small lists, and any team without an engineer to emit events. The setup is not hard, but it is not a marketing-team-only tool either.
Also skip it if you cannot afford $100/month for something that replaces a $20 tool. The event model only pays off once behaviour-based campaigns exist.
Key Takeaways
- Customer.io has no free tier; pricing starts near $100/month with profiles and sends metered separately.
- Connect via the Track API: identify with a permanent ID, then track events.
- Build one campaign on one event before expanding; set trigger frequency and quiet hours explicitly.
- Import suppression lists before the first send — they prevent deliverability damage.
- Verify in order: timeline event, message status, inbox receipt on your own domain.
