On this page
Customer.io: crm features and setup
An event-based customer engagement platform built around user data. It suits a digital product that wants to send messages based on user progress rather than only on a campaign date.
Tool by the Otomatzia editorial team · source content checked on
Overview
In Customer.io, automation quality depends on what product events mean: opening a screen does not necessarily mean an action was completed. It's a good idea to plan a short event dictionary and connect one journey to it, such as helping a user who signed up but did not finish setup. Also define what ends the journey, so a purchase or completion event cancels a reminder that is no longer relevant.
Features
- Journeys for building automated customer journeys
- Audience segmentation from data
- API and webhooks for connecting data and events
Business uses
- Guiding a user who has not completed a product activation step
- Stopping a reminder after the desired action is completed
Getting started
- Define event names and their meanings, and initially send events from a test account.
- Send the entry event twice from the same test user, and check whether it creates a duplicate journey entry or an extra profile you did not intend to create.
- Complete the action while the user is waiting for the next message, and confirm the journey stops even if the event arrives late or through another integration.
What to check
- Check user identification before and after login to prevent duplicate profiles.
- Review event delivery delays and the journey exit mechanism when the user's status changes.
Sources to check next
Vendor features and prices change. Confirm details on the linked official pages before you rely on them.