Journeys Message Metrics Source
Customer.io Journeys automatically acts as multiple sources of data in Data Pipelines: one source for Journeys Message Metrics and individual sources for each set of Journeys (Track) API credentials. This page is specifically about Journeys Message Metrics. If you want to learn more about using our Track API, web SDK, and mobile SDKs as Data Pipelines sources, see the Journeys API page.
How it works
Journeys captures events relating to message activity—the messages you send, whether or not people open them, when people click them, and so on.
By default, we also forward these events to Data Pipelines as a source. This is the default Journeys Message Metrics source that you see on the Connections page in Data Pipelines.


Treating incoming Journeys metrics as a source lets you send data to destinations that help you aggregate and analyze audience data, so you follow and chart how your audience reacts to different message channels in your marketing stack.
What metrics do we send to Data Pipelines?
Journeys Message Metrics are the same events we track with reporting webhooks. These include Customer subscribe/unsubscribe events, and events representing the message lifecycle for each message (email, SMS, push, etc).
Name | Description |
---|---|
customer_subscribed | A person’s “unsubscribed” attribute was explicitly set to “false” |
customer_unsubscribed | A person’s “unsubscribed” attribute was explicitly set to “true” |
cio_subscription_preferences_changed | A person changed their subscription preferences—either through our subscription center, or you changed their cio_subscription_preferences attribute values. Learn more about the subscription center. |
email_drafted | Customer.io successfully rendered a message and populated liquidA syntax that supports variables, letting you personalize messages for your audience. For example, if you want to reference a person’s first name, you might use the variable {{customer.first_name}} . for an individual recipient. The message is ready to send. |
email_attempted | An email that couldn’t be sent to the delivery provider will be retried |
email_deferred | An email that the delivery provider couldn’t send will be retried by the delivery provider |
email_sent | An email was sent from Customer.io to the delivery provider |
email_delivered | The delivery provider reported the email was delivered to an inbox |
email_opened | An email was opened |
email_clicked | A tracked link in an email was clicked |
email_converted | A person matched a conversion goal attributed to an email |
email_unsubscribed | A person unsubscribed via a particular email |
email_bounced | The delivery provider was unable to deliver the email |
email_dropped | An email wasn’t sent because it was addressed to a person who was suppressed |
email_spammed | An email was marked as spam by the recipient |
email_failed | An email couldn’t be sent to the delivery provider |
email_undeliverable | An email was undeliverable, likely because it hit a message limit |
push_drafted | Customer.io successfully rendered a push notification and populated liquidA syntax that supports variables, letting you personalize messages for your audience. For example, if you want to reference a person’s first name, you might use the variable {{customer.first_name}} . for an individual recipient. The message is ready to send. |
push_attempted | A push notification that couldn’t be sent to the delivery provider will be retried |
push_sent | A push notification was sent from Customer.io to the delivery provider |
push_delivered | A push notification was delivered to a recipient. You must use our SDKs or report delivered metrics to us using the API. |
push_opened | The app on a person’s device reported the push notification was opened. You must use our SDKs or report opened metrics to us using the API. |
push_clicked | A tracked link in a push notification has been clicked. Note that we do not track Clicked metrics or enable link tracking for push notifications by default. When a person taps a push notification, the message is marked as Opened. |
push_converted | A person matched a conversion goal attributed to a push notification |
push_bounced | The delivery provider reported at least one invalid device token |
push_dropped | A push notification wasn’t sent because at least one device token previously bounced |
push_failed | A push notification couldn’t be sent to the delivery provider |
push_undeliverable | A push notification was undeliverable, likely because it hit a message limit |
sms_drafted | Customer.io successfully rendered an SMS message and populated liquidA syntax that supports variables, letting you personalize messages for your audience. For example, if you want to reference a person’s first name, you might use the variable {{customer.first_name}} . for an individual recipient. The message is ready to send. |
sms_attempted | An SMS that couldn’t be sent to the delivery provider will be retried |
sms_sent | An SMS was sent from Customer.io to the delivery provider |
sms_delivered | The delivery provider reported the SMS was delivered |
sms_clicked | A tracked link in an SMS has been clicked |
sms_converted | A person matched a conversion goal attributed to an SMS |
sms_bounced | The delivery provider was unable to deliver the SMS |
sms_failed | An SMS couldn’t be sent to the delivery provider |
sms_undeliverable | An SMS message was undeliverable, likely because it hit a message limit |
slack_drafted | Customer.io successfully rendered a slack message and populated liquidA syntax that supports variables, letting you personalize messages for your audience. For example, if you want to reference a person’s first name, you might use the variable {{customer.first_name}} . for an individual recipient. The message is ready to send. |
slack_attempted | A slack message that couldn’t be sent will be retried |
slack_sent | A slack message was sent from Customer.io to slack |
slack_clicked | A tracked link in a slack message has been clicked |
slack_failed | A slack message couldn’t be sent to slack |
slack_undeliverable | A Slack message was undeliverable, likely because it hit a message limit |
webhook_drafted | Customer.io successfully populated a webhook with liquidA syntax that supports variables, letting you personalize messages for your audience. For example, if you want to reference a person’s first name, you might use the variable {{customer.first_name}} . and is ready to send it. |
webhook_attempted | A webhook that couldn’t be sent will be retried |
webhook_sent | A webhook was sent from Customer.io to the specified Webhook URL |
webhook_clicked | A tracked link in a webhook payload has been opened |
webhook_failed | A webhook couldn’t be sent to the specified Webhook URL |
webhook_undeliverable | A webhook was undeliverable, likely because it hit a message limit |
in_app_drafted | Customer.io successfully rendered an in-app message and is ready to send it. |
in_app_attempted | An in-app that couldn’t be sent will be retried |
in_app_sent | An in-app was sent. |
in_app_opened | An in-app was opened |
in_app_clicked | A tracked response in an in-app was clicked |
in_app_converted | A person matched a conversion goal attributed to an in-app |
in_app_failed | An in-app couldn’t be sent |
in_app_undeliverable | An in-app was undeliverable. |
Metric Events in Data Pipelines
We map properties from Journeys to Data Pipelines. You can see the complete list of properties in each event in our reporting webhooks. But we’ve provided an example below to show how a metric event recorded in Journeys maps to Data Pipelines.
The event name
is the channel and metric—like Email Opened
as shown in the example below.
The properties
object contains information about the customer, the message (delivery_id
), the campaign, broadcast, or transactional ID the message originated from, and so on.
{
"type": "track",
"event": "Email Opened",
"userId": "12345",
"messageId": "01H8F21G9KK14JKX233RDFJCNM",
"timestamp": "2023-08-22T16:42:55.003Z",
"sentAt": "2023-08-22T16:42:57.739Z",
"context": {
"integration": {
"name": "customer.io",
"version": "2.0.0"
},
"traits": {},
"ip": "35.225.6.73",
"userAgent": "Customer.io/go1.20.4 (test; +https://customer.io/actions)"
},
"properties": {
"customer_id": "12345",
"delivery_id": "RKK4AwUAAYoeIC5PHMYd6-vTAYhWkQ==",
"recipient": "cool.person@example.com",
"subject": "Password reset request",
"transactional_message_id": 8,
"userId": "12345"
},
"integrations": {
"Customer.io": false,
"Customer.io (Actions)": false
},
"receivedAt": "2023-08-22T16:42:57.742Z",
"originalTimestamp": "2023-08-22T16:42:55.000Z"
}