What Customer.io is
Customer.io is a messaging platform built around event-driven automation across email, push, SMS and in-app.
Its whole model depends on receiving events that are accurate and attributed to the right person.
- Home
- Integrations
- Customer.io
Customer.io integration: server-side events resolved to a known profile
Forward identity-resolved events to Customer.io so campaigns and journeys trigger on what the customer actually did.
- Role
- Destination
- Category
- Email & SMS
- Plans
- All plans
About Customer.io
Upstack forwards identity-resolved events, so a profile represents a customer rather than a browser.
Journeys then branch on what the person actually did across devices. That is the difference between an abandonment message that makes sense and one arriving after they already bought.
How Customer.io works
Customer.io triggers campaigns and journeys from events sent through its API, evaluated against a person profile. If the same human arrives as two profiles, they receive two versions of every journey and neither is complete.
What you can do with it
Three jobs this connector does inside Customer.io.
01
Send complete conversions
Conversions reach Customer.io through its server-side API with restored click IDs and hashed identifiers attached, so more of what you send is matched on arrival, and the conversions you never saw stop being invisible.
02
Optimize on the customer you want
Map any order attribute to the conversion Customer.io receives (profit rather than revenue, new customers rather than repeat buyers, high-value orders rather than every checkout), so the platform learns from the buyers worth acquiring.
03
Journeys that branch on the whole customer
Events arrive resolved across devices, so automation responds to everything the person did rather than one browser session.
Documentation
Set-up reference.
Set-up, event schema and field mapping for Customer.io as a destination.
FAQ
Customer.io integration questions.
What does Upstack send to Customer.io?
Forward identity-resolved events to Customer.io so campaigns and journeys trigger on what the customer actually did.
Which plans include the Customer.io integration?
All plans. Upstack has three plans that scale with your order volume, and the same integrations are on every plan.
Will Upstack slow down my store?
Upstack’s own pixel loads asynchronously and fails silently, so it doesn’t hold up your pages. What each destination adds depends on its Tracking Method. The default, Browser + Server, loads that platform’s own tag on your store, in place of the copy you would otherwise install yourself, and also sends the same events from Upstack’s servers. Choose Server for any destination that offers it and its tag never loads, while its events still arrive from Upstack’s servers.
Similar integrations
Other destinations to send to.
-
Klaviyo Flows fire for visitors the pixel lost. -
Attentive SMS journeys triggered on people, not sessions. -
Postscript SMS flows reach subscribers the pixel missed. -
Omnisend Resolved events for email and SMS automation. -
Sendlane Retention flows on resolved customers. -
Alia Post-purchase capture, resolved. -
Meta Conversions API Conversions API with higher Event Match Quality. -
Google Ads Conversions Enhanced Conversions that actually match. -
TikTok Events API Events API with a resolved customer attached. -
Pinterest Conversions API, deduplicated server-side. -
Snapchat Conversions API with restored identifiers. -
Reddit Conversions API for a community-led audience.
Get Customer.io tracking right.
A 15-minute walkthrough tailored to your stack and channels.