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.

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

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

Destination Settings

Setting	Description
Account Region	Learn about Account Regions.
API Key	Required. Customer.io API key. This can be found on your API Credentials page.
Site ID	Required. Customer.io site ID. This can be found on your API Credentials page.

Available Presets

Customer.io (Actions) has the following presets:

Preset Name	Trigger	Default Action
Create or Update Device	Event event = "Application Installed" Event event = "Application Opened"	Create or Update Device
Report Delivery Event	Event event = "Report Delivery Event"	Report Delivery Event
Track Event	Event type = "track" and event != "Relationship Deleted" and event != "User Deleted" and event != "User Suppressed" and event != "User Unsuppressed" and event != "Object Deleted" and event != "Report Delivery Event"	Track Event
Create or Update Person	Event type = "identify"	Create or Update Person
Track Screen View	Event type = "screen"	Track Screen View
Track Page View	Event type = "page"	Track Page View
Create or Update Object	Event type = "group"	Create or Update Object

Available Actions

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

• Create or Update Person

• Track Event

• Create or Update Device

• Track Page View

• Delete Device

• Track Screen View

• Create or Update Object

• Delete Relationship

• Unsuppress Person

• Merge People

• Delete Object

• Suppress Person

• Delete Person

• Report Delivery Event

Create or Update Person

Create a person in Customer.io or update them if they exist.

Create or Update Person is a Cloud action. The default Trigger is: type = "identify"

Click to show / hide fields

Track Event

Track an event for a known or anonymous person.

Track Event is a Cloud action. The default Trigger is: type = "track" and event != "Relationship Deleted" and event != "User Deleted" and event != "User Suppressed" and event != "User Unsuppressed" and event != "Group Deleted" and event != "Report Delivery Event"

Click to show / hide fields

Create or Update Device

Create or update a person’s device.

Create or Update Device is a Cloud action. The default Trigger is: type = "track" and event = "Application Installed"

Click to show / hide fields

Track Page View

Track a page view for a known or anonymous person.

Track Page View is a Cloud action. The default Trigger is: type = "page"

Click to show / hide fields

Delete Device

Delete a person’s device.

Delete Device is a Cloud action. The default Trigger is: event = "Application Uninstalled" or event = "Device Deleted"

Click to show / hide fields

Track Screen View

Track a screen view for a known or anonymous person.

Track Screen View is a Cloud action. The default Trigger is: type = "screen"

Click to show / hide fields

Create or Update Object

Create an object in Customer.io or update them if they exist.

Create or Update Object is a Cloud action. The default Trigger is: type = "group"

Click to show / hide fields

Delete Relationship

Delete a relationship between a person and an object in Customer.io.

Delete Relationship is a Cloud action. The default Trigger is: event = "Relationship Deleted"

Click to show / hide fields

Unsuppress Person

Unsuppress a person in Customer.io. This will allow the person to receive messages again.

Unsuppress Person is a Cloud action. The default Trigger is: event = "User Unsuppressed"

Click to show / hide fields

Merge People

Merge two customer profiles together.

Merge People is a Cloud action. The default Trigger is: type = "alias"

Click to show / hide fields

Delete Object

Delete an object in Customer.io.

Delete Object is a Cloud action. The default Trigger is: event = "Object Deleted"

Click to show / hide fields

Suppress Person

Suppress a person in Customer.io. This will prevent the person from receiving any messages.

Suppress Person is a Cloud action. The default Trigger is: event = "User Suppressed"

Click to show / hide fields

Delete Person

Delete a person in Customer.io.

Delete Person is a Cloud action. The default Trigger is: event = "User Deleted"

Click to show / hide fields

Report Delivery Event

Report delivery metrics for a message sent from the Customer.io Journeys product.

Report Delivery Event is a Cloud action. The default Trigger is: event = "Report Delivery Event"

Click to show / hide fields

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

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

Convert timestamps

When you map some actions, you’ll see a Convert Timestamps setting. This setting is on by default, and converts traits containing ISO-8601 timestamps to Unix timestamps (seconds since epoch). Segment recommends that you leave this setting enabled. While Segment does support ISO-8601 timestamps in liquid, you must use Unix timestamps to take advantage of timestamp conditions when segmenting your audience in Customer.io.

For example, if you send an event with a purchase_time trait of 2006-01-02T18:04:07Z, Customer.io converts it to 1136253847. If the timestamp is not in ISO-8601 format, Customer.io doesn’t convert it. This avoids inadvertently converting values like phone numbers or IDs.

Customer.io makes an exception for the created_at trait, converting ISO-8601 timestamps or any values supported by JavaScript Date objects to Unix timestamps.

Device token collection

Segment does not automatically collect push notification tokens. These parameters are required by Customer.io, requiring logic to be implemented to collect these values. As an example, you can use this plugin to collect the Firebase Cloud Messaging device token for React Native.

In-App Messaging

The Customer.io Actions destination is built and maintained by Segment’s partner Customer.io, and does not currently support in-app messaging. Segment recommends reaching out to them to express your interest in using in-app messaging with the Segment integration.