Source catalog

Journeys captures unsubscribe events and message metrics—when you send a message, when your audience opens a message, and so on. We forward these events to Data Pipelines, so you can use them in downstream applications that help you track performance over time.

The Journeys API was how you sent data to Customer.io before we introduced Data Pipelines. Journeys API sources let you use Data Pipelines without changing your existing integrations by automatically translating incoming Journeys Track API calls to our Data Pipelines format. You’ll use this source for each set of Journeys API credentials that you want to connect to Data Pipelines.

The Salesforce source lets you send data from your CRM to destinations where you can activate it. For example, you can send Salesforce data to Customer.io where you can automatically message people—follow up with leads, message contacts when it’s time to renew their contracts, and so on. This makes Salesforce a part of your larger marketing stack without needing developers to write a complicated integration.

Add our JavaScript library to your website or app to send events representing your website visitors and users to one or more destinations. This library makes it easy—and in some cases, automatic—to send events into Customer.io and other destinations.

You can integrate directly with our REST API if you don’t want to install one of our libraries or you want to support a source that we don’t have a native integration with.

Add our NodeJS library to your project to send events representing your website visitors and app users. This library saves you the trouble of writing your own code to send events into Customer.io and other destinations—either from your Node backend or client-side functions.

Add our Go library to your project to send server-side events representing your audience’s activities. This library saves you the trouble of writing your own code to send events into Customer.io and other cloud-based destinations.

Add our Python library to your project to send server-side events representing your audience’s activities. This library saves you the trouble of writing your own code to send events into Customer.io and other cloud-based destinations.

Import data from Google BigQuery to any destination. This source saves you the trouble of writing code to extract, transform, and load data from your warehouse. Instead, specify the query (or queries) to run, and we’ll handle the rest.

Import data from Amazon Redshift to any destination. This source saves you the trouble of writing code to extract, transform, and load data from your warehouse. Instead, specify the query (or queries) to run, and we’ll handle the rest.

Import data from Snowflake to any destination. This source saves you the trouble of writing code to extract, transform, and load data from your warehouse. Instead, specify the query (or queries) to run, and we’ll handle the rest.

Import data from MySQL to any destination. This source saves you the trouble of writing code to extract, transform, and load data from your database. Instead, specify the query (or queries) to run, and we’ll handle the rest.

Import data from PostgreSQL to any destination. This source saves you the trouble of writing code to extract, transform, and load data from your database. Instead, specify the query (or queries) to run, and we’ll handle the rest.

Import data from Microsoft SQL Server to any destination. This source saves you the trouble of writing code to extract, transform, and load data from your database. Instead, specify the query (or queries) to run, and we’ll handle the rest.

Add our iOS library to your app to send push notifications and in-app messages to your app’s users and track your audience’s activities in your app. You can add iOS as a mobile source in CDP, then route events to your journeys instance.

Add our Android library to your app to send push notifications and in-app messages to your app’s users and track your audience’s activities in your app. The library sends data directly to Journeys via our Track API, but the events are available via the “Journeys API” source in Data Pipelines.

Add our React Native library to your app to send push notifications and in-app messages to your app’s users and track your audience’s activities in your app. The library sends data directly to Journeys via our Track API, but the events are available via the “Journeys API” source in Data Pipelines.

Add our Flutter library to your app to send push notifications and in-app messages to your app’s users and track your audience’s activities in your app. The library sends data directly to Journeys via our Track API, but the events are available via the “Journeys API” source in Data Pipelines.

Use our Expo plugin for your React Native app to send push notifications and in-app messages to your app’s users and track your audience’s activities in your app. The library sends data directly to Journeys via our Track API, but the events are available via the “Journeys API” source in Data Pipelines.