Customer.io Connector

Last updated:

What does the Customer.io Connector app do?

The Customer.io Connector sends event data from PostHog into Customer.io. User emails will also be sent if available and customers will be created in Customer.io.

What are the requirements for this app?

The Customer.io Connector requires either PostHog Cloud, or a self-hosted PostHog instance running version 1.30.0 or later.

Not running 1.30.0? Find out how to update your self-hosted PostHog deployment!

You'll also need access to the relevant Customer.io account.

How do I install the Customer.io Connector app?

  1. Visit the 'Apps' page in your instance of PostHog.
  2. Search for 'Customer.io' and select the app, press Install.
  3. Add your Customer.io site ID and token at the configuration step.
  4. Enable the app and watch your 'People' list get populated in Customer.io!

Configuration

OptionDescription
Customer.io Site ID
Type: string
Required: True
Provided during Customer.io setup.
Customer.io API Key
Type: string
Required: True
Provided during Customer.io setup.
Tracking Endpoint
Type: choice
Required: False
Use the EU variant if your Customer.io account is based in the EU region.
Identify by email
Type: choice
Required: False
If enabled, the plugin will identify users by email instead of ID, whenever an email is available.
Filtering of Anonymous Users
Type: choice
Required: False
Customer.io pricing is based on the number of customers. This is an option to only send events from users that have been identified. Take into consideration that merging after identification won't work (as those previously anonymous events won't be there).
PostHog Event Allowlist
Type: string
Required: False
If this is set, only the specified events (comma-separated) will be sent to Customer.io.

How do I match persons in PostHog with customers in Customer.io?

We assume that you use the same ID to identify users in Customer.io as you use as distinct_id or in posthog.identify().

How do I set properties on a Customer.io customer via PostHog?

PostHog will send any property inside the $set: {} property to customer.io. In the example below, email and userProperty will be set on the customer

JavaScript
posthog.capture(
'some event',
{
event_property: 'this will not get sent',
$set: {
email: 'test@example.com',
userProperty: 'value'
}
}
)

Is the source code for this app available?

PostHog is open-source and so are all apps on the platform. The source code for the Customer.io Connector is available on GitHub.

Who created this app?

We'd like to thank PostHog team members Yakko Majuri and Marius Andra, Michael Matloka and community members Angela Purcell, Conrad Kurth and Alberto S for creating the Customer.io Connector.

Who maintains this app?

This app is maintained by PostHog. If you have issues with the app not functioning as intended, please raise a bug report to let us know!

What if I have feedback on this app?

We love feature requests and feedback! Please create an issue to tell us what you think.

What if my question isn't answered above?

We love answering questions. Ask us anything via our Support page.

You can also join the PostHog Community Slack group to collaborate with others and get advice on developing your own PostHog apps.

Questions?

Was this page useful?

Next article

Databricks Export

What does the Databricks Export app do? The Databricks Export app for PostHog will push data from PostHog to Databricks, once every minute. The app creates a table and migrates data from DBFS to a database. What are the requirements for this app? Using this app requires either PostHog Cloud, or a self-hosted PostHog instance running version 1.30.0 or later. Not running 1.30.0? Find out how to update your self-hosted PostHog deployment ! How do I install the Databricks Export app for PostHog…

Read next article