Home
/
Connections
/
Destinations
/
Catalog
/
Customer.io (Actions) Destination

Customer.io (Actions) Destination

Customer.io lets you send automated email, push, SMS, letters, and webhooks based on your customer’s activities in your app or product. It makes conversion tracking, optimization and remarketing easier.

This document is about a feature which is in beta. This means that the Destination Actions are in active development, and some functionality may change before it becomes generally available

Good to know: This page is about the Actions-framework Customer.io Segment destination. There’s also a page about the non-Actions Customer.io destination. Both of these destinations receives data from Segment. There’s also the Customer.io source, which sends data to Segment!

Benefits of Customer.io (Actions) vs Customer.io classic

Track an anonymous event. Track events from users who are not yet known to Customer.io. If you have the Customer.io event merging feature enabled, Customer.io associates all incoming events that share an anonymous_id received in the last 30 days.

Getting started

From the Segment web app, click Catalog, then click Destinations.
Find the Destinations Actions item in the left navigation, and click it.
Select Customer.io (Actions).
Click Configure Actions Customer.io.
Select an existing Source to connect to Customer.io (Actions).
Enter the API Key and Site ID. Find these values on the Customer.io API Credentials Page.
Select Quick Setup to start with pre-populated subscriptions, or Customized Setup to configure each action from scratch. Click Configure Actions.

Prebuilt subscriptions

Subscription Name	Trigger	Customer.io Action
Track Event	All Track calls from the connected source.	Track Event
Create or Update Person	All Identify calls from the connected source.	Create or Update Person
Create or Update Device	All Track calls where the Event Name is `Application Installed`.	Create or Update Device

Available Customer.io actions

Build your own subscription. Combine the supported triggers with the following Customer.io-supported actions:

Track Event
Create or Update Person
Create or Update Device
Track Anonymous Event

Track Event

Track an event for a known person.

Click to expand fields

Field	Description
Event Name (required)	Default `event` The name of the event.
Person ID	Default `userId` The ID of the person who triggered the event.
Anonymous ID	Default `anonymousId` The Anonymous ID of the person who triggered the event.
Event Type	Default `type` Override the event type. For example, “page”.
Data	Default `properties` Any customer data to include with the event.

Create or Update Person

Update a person in Customer.io or create them if they don’t exist.

Click to expand fields

Field	Description
Person ID (required)	Default `userId` The identifier used to uniquely identify a person in Customer.io
Email Address (required)	Default `traits.userId` The email address of the person.
Anonymous ID	Default `anonymousId` The Anonymous ID to uniquely identify a person in Customer.io.
Created At	Default `timestamp` The timestamp for when this person was created.
Custom Attributes	Default `traits` Optional custom attributes for this person. When you update a person, attributes are added and not removed.

Create or Update Device

Update a person’s device in Customer.io, or create it if it doesn’t exist.

Click to expand fields

Field	Description
Person ID (required)	Default `userId` The ID of the person this device belongs to.
Device ID (required)	Default `context.device.id` The unique ID for the device from which the event was sent.
Platform (required)	Default `context.device.type` The platform of the device.
Last Used	Default `timestamp` The timestamp for when the device was last used.

Track Anonymous Event

Track an event not tied to a known person.

Click to expand fields

Field	Description
Event Name (required)	Default `event` The name of the event.
Data	Default `properties` Custom data to include with the event. If `recipient`, `from_address`, or `reply_to` are sent, they will override settings on any campaings triggered by this event. `recipient` is required if the event is used to trigger a campaign.

Migration from Customer.io classic

Keep the following in mind if you plan to move to Customer.io (Actions) from the classic Customer.io destination.

Customer-io settings mapping

All Cloud Device-web

customer-io Classic Destination Setting	How to enable in customer-io (Actions)
Connection Settings
API Key Cloud Device-web	Set the API key as a connection setting during initial configuration, or on the Settings tab.
Customer.io Datacenter Cloud Device-web	Select the Account Region in Connection Settings.
Site ID Cloud Device-web	Set the Site ID as a connection setting during initial configuration, or on the Settings tab.
Connection Mode Cloud Device-web	Customer.io (Actions) supports cloud-mode.
Other Settings
Convert to Unix Time Cloud Device-web	tbd

This page was last modified: 05 Nov 2021

Need support?

Questions? Problems? Need more info? Contact us, and we can help!

Visit our Support page

Was this page helpful?

Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.

Create free account