IntegrationEmail / Marketing destination
Customer.io Integration - Track Behavioral Events from Product Activity
Meshes routes product events into Customer.io through the Pipelines API, identifying users and tracking behavioral events so your messaging automation always starts from real product signals.
user.signuptrial.startedfeature.used|Actionstrack_eventThe event names shown here are examples. In Meshes, event types are fully customized for each organization.
What you can do
Supported actions with real product context behind them
Create the Customer.io connection in Meshes with a CDP API Key. Choose your workspace region (US or EU) and enter the key from Customer.io workspace → Data & Integrations → Integrations → Customer.io API. Meshes handles identify and track calls automatically.
Customer.io is where behavioral segmentation becomes operational. When user.signup or feature.used happens, teams want the person identified, the event tracked, and downstream campaigns ready to react immediately.
Meshes keeps that logic in the event-routing layer instead of your application handlers or background workers. You emit the event once, map the fields in your Meshes workspace, and let Meshes handle delivery, retries, and replay if Customer.io is temporarily unavailable.
track_eventIdentify users and track behavioral events
Identify the person in Customer.io and track the behavioral event so campaigns, broadcasts, and segments can react to real product activity.
Common use cases
How Meshes teams usually put Customer.io to work
These are the workflows where this destination tends to matter first. The point is to keep the product event, the destination action, and the operational retry path in one place.
Identify users and start onboarding campaigns on signup
Use user.signup to identify the new person in Customer.io and track the signup event so behavioral onboarding campaigns can begin immediately.
Track feature adoption for lifecycle segmentation
Use feature.used to tell Customer.io when users reach milestones so campaigns and in-app messages can react to actual product behavior.
Trigger win-back campaigns from trial expiry signals
Track trial.expired so Customer.io can start win-back or re-engagement campaigns the moment the trial window closes.
See the trial-expiry use caseKeep behavioral context accurate without custom tracking code
Let the Meshes event layer own Customer.io identification and event tracking so behavioral state reflects product reality without adding CDP calls to every handler.
How it works
Connect the destination, define the rule, emit the event
In Meshes, the operating model is simple: create the connection in the workspace, create the rule, then let the event delivery layer handle the last mile.
Connect Customer.io
Create the Customer.io connection in Meshes with your CDP API Key and region. Meshes will use the Pipelines API to identify users and track events.
Create routing rules in Meshes
Create rules for events like user.signup or feature.used, choose track_event, and map userId, email, or anonymousId. Any other top-level payload fields become Customer.io profile traits automatically.
Emit the event and review delivery
Emit the product event from your app or use Send Test Event in Meshes. Meshes identifies the person and tracks the event in Customer.io, retries transient failures, and keeps full delivery history for replay.
Event example
Emit the product event once
import MeshesEventsClient from '@mesheshq/events';
const meshes = new MeshesEventsClient(
process.env.WORKSPACE_PUBLISHABLE_KEY!,
);
await meshes.emit({
event: 'user.signup',
resource: 'subscription_plan',
resource_id: 'growth',
payload: {
userId: 'usr_2048',
email: 'alex@northstar.io',
first_name: 'Alex',
last_name: 'Nguyen',
plan: 'starter',
source: 'website',
},
});Connection model
CDP API Key
Create the Customer.io connection in Meshes with a CDP API Key. Choose your workspace region (US or EU) and enter the key from Customer.io workspace → Data & Integrations → Integrations → Customer.io API. Meshes handles identify and track calls automatically.
Why Meshes
Why teams use Meshes for Customer.io
The benefit is not just that the destination is supported. It is that the destination sits inside the same fan-out, retry, replay, and delivery-visibility layer as the rest of your stack.
Identify and track run from the same delivery layer
Meshes sends both the identify and track calls to Customer.io from a single product event, using userId, email, or anonymousId while applying extra payload fields as profile traits.
Retries protect campaign triggers
A transient Customer.io failure does not have to become missing behavioral state. Meshes captures the attempt, retries it, and lets you replay after a fix.
Behavioral tracking can fan out with CRM and email
The same signup event can identify the user in Customer.io while updating CRM, sending a welcome email, and alerting internal channels in parallel.
It works for customer-facing integrations too
If you expose Meshes workspaces to customers, each workspace can connect its own Customer.io account while your product keeps one event-emission path.
Keep exploring
Related guides, use cases, docs, and comparison pages
These links are the next layer down: concrete patterns, supporting documentation, and the build-vs-buy context that usually comes up during evaluation.
Catalog
All integrations
Browse the full destination catalog and compare Customer.io with the rest of the Meshes integration surface.
Open linkDocs
Customer.io integration docs
Customer.io connection flow, rule setup, and testing steps in the product docs.
Open linkUse Case
User signup fan-out
Example of one signup event updating CRM, lifecycle email, behavioral tracking, and internal alerts at the same time.
Open linkGuide
Routing guides
Additional Meshes patterns that can be adapted for behavioral event tracking and lifecycle delivery.
Open linkCompare
Meshes vs. DIY
Breakdown of what it costs to own Customer.io retries, field mapping, replay, and delivery visibility yourself.
Open link