Feed data into Customer.io

You'll use the Track API to get data about People and Objects into Customer.io, including—but not limited to:

• Identify people: Add people to your workspace
• Send events: Represent your audience's activity on your website or in your app
• Relate people to objects: Objects are a grouping mechanism that let you set up relationships, like accounts that people belong to, online courses that they enroll in, or recreational leagues that people might join

You can use our Web SDK or our client libraries to take advantage of this API without writing your own requests from scratch.

Set up a backend integration

You'll use our App API to integrate with your backend apps, hence the name. You can use this API to:

• Trigger messages: Send API-triggered broadcasts and transactional messages
• Find people: We support complex filters that help you find members of your audience who meet specific criteria
• Get campaigns, broadcasts, and messages: Lookup information about your workflows and individual messages
• Add collections update snippets: Add and update assets that help you personalize messages or reuse data across emails
• Import and export bulk data: Import and export people in bulk

Trigger messages

Our App API has two endpoints designed specifically to trigger messages:

Transactional messages represent information that your customer implicitly requests—like password reset requests, purchase receipts, and so on. You can pass your entire message to this endpoint, so you can both compose and trigger messages from your backend integration.

API-triggered broadcasts let you trigger a message from your app or a backend integration to an audience of people. For example, you might send a broadcast to a group of people interested in an event when tickets go on sale.

Capture granular metrics

Reporting webhooks let you subscribe to specific channels and metrics, so that you can report information about message performance and how your audience responds to messages to your app asynchronously.