Customer.io, joined, in and out.
DataGlue marries Customer.io data with your other systems and sends outcomes back. Every number shows its formula and its records.
Customer.io: A messaging platform for email, SMS and push campaigns driven by customer data and events.
- IN + OUT
- NATIVE
Bring Customer.io and one decision to the call. Tool names are enough; no access needed.
Trusted by
- NativeIN + OUT
- WebhookIN + OUT
- REST APIIN + OUT
What moves between Customer.io and DataGlue. Sends, opens, clicks, bounces and unsubscribes come in on each person's timeline. Allowlisted profile fields and events go out.
- IN + OUTNATIVE
Native
A native connection, built and running today. Signed email activity arrives on each person's timeline, kept apart from revenue. An allowlisted set of profile fields and the events you pick are sent back.
- IN + OUT
Webhook
INCustomer.io sends a webhook to a DataGlue inbound URL when a record is created or changes. Fields map to people and events once, in the build. Every fact keeps Customer.io as its source.
OUTDataGlue sends signed webhooks to Customer.io on the events and conversions you pick, with filters.
- IN + OUT
REST API
INCustomer.io records are sent to our REST API with a scoped key, as events and linked ids on the same person. The calls are set up in the build.
OUTPeople, sessions, events and conversions are read from our REST API with a scoped key and written into Customer.io.
Connections are agreed in the build. We check the source data, consent and identifiers before promising a linked journey. Customer.io is a trademark of its owner; this page implies no partnership or endorsement.
Describe the outcome. DataGlue works it out and shows you the formula.
- 01
Describe the outcome you want in plain words, such as "Email that led to a booking".
- 02
DataGlue works it out from the definitions of your data sources, Customer.io included, and shows the formula in concise English.
- 03
Send it on: to reports, BI tools, any destination, or the AI tools your team already uses.
- EXAMPLE OUTCOME 01
Email that led to a booking
THE FORMULABookings where the person clicked a campaign email in the seven days before, by campaign.
- EXAMPLE OUTCOME 02
Unsubscribes by journey
THE FORMULAUnsubscribes, split by the pages and forms each person saw before they joined the list.
Want one of these from your Customer.io data? We map the route and the first outcome on the call.
Book a CallBring Customer.io and one decision. We'll map the route and the first outcome on the call.
The call scopes fit. The build is a separate engagement, priced before work begins.