Customer.io
Each event flows to Customer.io's Track API v2 attached to the person — and triggers the campaigns and journeys you build there, with real behavior from site, checkout and CRM.
Data delivered
Data delivered
- Named events with full attributes
- Consistently identified person
- Real event timestamps
What it is for
What you can do with it
- Trigger abandoned-cart campaigns from the CDP event
- Sync behavior the site snippet can't reach
Why integrate
The business reason, not just the tech
Campaigns driven by the right event
Gateway cart abandonment, failed charges, upgrades — server events become journey triggers in Customer.io the minute they happen.
One person across systems
The identifier is the CDP one: whoever converted on the ad, replied to the email and purchased is ONE person in your campaigns.
How to connect
Step by step
- Step 1
Copy the site id and Track api key in Customer.io.
- Step 2
Create the destination with both credentials.
- Step 3
Create a Delivery with the events.
Frequently asked questions
What about anonymous visitors?
Events without an identified person are skipped — in Customer.io an event exists to move a person through campaigns. Once the visitor identifies, subsequent events join the profile.
Start measuring what actually becomes revenue
Create a free account, connect your first source and see your first lead timeline today. No card required.