Sample JSON to define the source schema for Customer.io

Before creating a Customer.io source connection, you will require a source schema to be provided. You can use the below JSON.

{
  "event_id": "01E4C4CT6YDC7Y5M7FE1GWWPQJ",
  "object_type": "customer",
  "metric": "subscribed",
  "timestamp": 1613063089,
  "data": {
    "customer_id": "42",
    "email_address": "test@example.com",
    "identifiers": {
      "id": "42",
      "email": "test@example.com",
      "cio_id": "d9c106000001"
    }
  }
}

Create an Experience Platform schema for Customer.io

You must also ensure that you create an Experience Platform schema to use for your source. See the tutorial on creating an Experience Platform schema for comprehensive steps on how to create a schema.

Experience Platform UI screenshot showing an example schema for Customer.io

Connect your Customer.io account

In the Experience Platform UI, select Sources from the left navigation to access the Sources workspace and see a catalog of sources available in Experience Platform.

Use the Categories menu to filter sources by category. Alternatively, enter a source name in the search bar to find a specific source from the catalog.

Go to the Marketing automation category to see the Customer.io source card. To begin, select Add data.

Experience Platform UI screenshot for catalog with Customer.io card

Select data

The Select data step appears, providing an interface for you to select the data that you want to bring to Experience Platform.

  • The left part of the interface is a browser that allows you to view the available data streams within your account;
  • The right part of the interface lets you preview up to 100 rows of data from a JSON file.

Select Upload files to upload a JSON file from your local system. Alternatively, you can drag and drop the JSON file you want to upload into the Drag and drop files panel.

The add data step of the sources workflow.

Once your file uploads, the preview interface updates to display a preview of the schema you uploaded. The preview interface allows you to inspect the contents and structure of a file. You can also use the Search field utility to access specific items from within your schema.

When finished, select Next.

The preview step of the sources workflow.

Dataflow detail

The Dataflow detail step appears, providing you with options to use an existing dataset or establish a new dataset for your dataflow, as well as an opportunity to provide a name and description for your dataflow. During this step, you can also configure settings for Profile ingestion, error diagnostics, partial ingestion, and alerts.

When finished, select Next.

The dataflow-detail step of the sources workflow.

Mapping

The Mapping step appears, providing you with an interface to map the source fields from your source schema to their appropriate target XDM fields in the target schema.

Experience Platform provides intelligent recommendations for auto-mapped fields based on the target schema or dataset that you selected. You can manually adjust mapping rules to suit your use cases. Based on your needs, you can choose to map fields directly, or use data prep functions to transform source data to derive computed or calculated values. For comprehensive steps on using the mapper interface and calculated fields, see the Data Prep UI guide.

All the mappings listed below are mandatory and should be setup before proceeding to the Review stage.

Target Field
Description
object_type
The object type, refer to the Customer.io events documentation for the supported types.
id
The object’s identifier.
email
The email address associated with the object.
event_id
The unique identifier of the event.
cio_id
The Customer.io identifier for the event.
metric
The event type. For more information, refer to the Customer.io events documentation for supported types.
timestamp
The timestamp when the event occurred.
IMPORTANT
Do not map cio_id when executing Customer.io webhook in the test mode as there will be no associated fields sent from Customer.io.

Once your source data is successfully mapped, select Next.

The mapping step of the sources workflow.