Skip to main content
Customer.io receives your shipment, order and tracking events and files them under the matching person. In Customer.io you can use those events to start campaigns, for example an email when the parcel is on its way. Customer.io sends the messages from your own Customer.io account; Zippendo only passes on the events. Integrations are included on every plan. Testing, the delivery log, editing and disconnecting work the same for every app: see Connect an integration. The longer guide is Customer.io.

​
Before you start

You need three things from your Customer.io account:
  • Site ID and API key: the tracking credentials Customer.io lists under API and webhook credentials in your account settings.
  • Your data region: whether your Customer.io account is hosted in the US or the EU.
Customer.io documentation explaining the Site ID and API key

Customer.io's guide to the Site ID and API key

​
Connect Customer.io

1

Find Customer.io in the catalog

Click Apps & integrations in the sidebar, then Catalog. Customer.io is under Apps. Click Connect, or Add connection if you already have one.
2

Review access

Read what Zippendo will do with the connection and click Continue.
3

Fill in the connection details

Type a Connection name, such as “Customer.io campaigns”. Paste your Site ID and API key. Then open the Data region list and pick US (track.customer.io) or EU (track-eu.customer.io).
4

Pick the events

Tick the events Customer.io should receive, or click Select all. See the list below.
5

Click Connect

You see Integration connected, and Customer.io shows on the Connected tab.
If Connect stays gray although everything is filled in, open the Data region list and pick your region, even if it already shows US.
Catalog with the Customer.io card and its Use in automations, Read more and Connect buttonsCatalog with the Customer.io card and its Use in automations, Read more and Connect buttons

The Customer.io card in the catalog

Connection window for Customer.io with a connection name, Site ID, API key, Data region and event checkboxesConnection window for Customer.io with a connection name, Site ID, API key, Data region and event checkboxes

Connecting Customer.io: a name, Site ID, API key and Data region

Pick the right Data region. With the wrong one, Customer.io refuses every event as if the Site ID and API key were wrong. An account hosted in the EU needs EU (track-eu.customer.io).

​
Events Customer.io can receive

Customer.io connection window scrolled to the order and tracking event checkboxesCustomer.io connection window scrolled to the order and tracking event checkboxes

The order and tracking events for Customer.io

In Customer.io the events keep Zippendo’s names, such as shipment.dispatched for Shipment sent. Customer.io files each event under the person with the customer’s email. An event without a customer email is recorded as an anonymous event. To give an event a different name, send it from an automation and fill in Custom event name (see below). The connection window has no field for it.

​
Check the connection

Click the paper plane on the connection row (Send test event), then open the delivery log (the plug icon). A test event has no customer, so Customer.io records it as an anonymous event. A green tick means your details work. 401 or 403 means Customer.io refused them: check the Site ID, the API key and the Data region.
Connected tab with a Customer.io connection and the test, delivery log, edit and delete iconsConnected tab with a Customer.io connection and the test, delivery log, edit and delete icons

A Customer.io connection on the Connected tab

Delivery log window for a Customer.io connection saying No deliveries yetDelivery log window for a Customer.io connection saying No deliveries yet

The delivery log before the first event

​
Change the details or disconnect

Click the sliders icon to open Edit your Customer.io connection. Leave Site ID and API key empty to keep what is stored.
If you change any of the three, fill in Site ID and API key and pick the Data region again. Whatever you enter replaces everything stored for the connection. The Data region list always shows US here and does not remember an EU choice, so a connection saved without picking a region uses US.
Click Save changes.
Edit window for a Customer.io connection with the connection name, empty credential fields, Data region and the eventsEdit window for a Customer.io connection with the connection name, empty credential fields, Data region and the events

Edit a Customer.io connection

To disconnect, click the trash can, type DELETE and click Disconnect. This stops all events to Customer.io and deletes the delivery log.
Disconnect integration window asking you to type DELETEDisconnect integration window asking you to type DELETE

Type DELETE to disconnect

​
Use Customer.io in an automation

In Automations, add the step Send Customer.io event. It sends the event that started the automation to Customer.io, but only when your conditions match. See Automations for building the rest of the automation.