Skip to main content
Forward Zippendo events to Customer.io to send messages about orders and deliveries, such as 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.
Product overview: Customer.io on zippendo.com

​
Before you start

  • Your Customer.io Site ID and API key, found under API and webhook credentials in your Customer.io settings.
  • Whether your Customer.io account is hosted in the US or the EU.
  • The Growth, Pro or Enterprise plan in Zippendo.

​
Events Customer.io can receive

  • Shipments: Shipment created, Shipment sent, Shipment cancelled
  • Orders: Order created, Order updated
  • Tracking: Tracking updated
To give an event another name in Customer.io, send it from an automation with Custom event name filled in.

​
Connect Customer.io

1

Open the catalog

Click Apps & integrations in the sidebar, then Catalog, and click Connect on Customer.io under Apps. Read what Zippendo will do and click Continue.
2

Enter your details

Type a Connection name, add the Site ID and API key, and pick your region in the Data region list: US (track.customer.io) or EU (track-eu.customer.io).
3

Pick the events

Tick the events Customer.io should receive.
4

Connect and test

Click Connect, send a test event from the connection (the paper plane), and check the delivery log (the plug icon) for a green tick.
With the wrong Data region, 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).
Every field and message is described in Connect Customer.io.

​
After connecting

  • Use the events in Customer.io campaigns and broadcasts.
  • Use Automations if only some events should reach Customer.io, or if your campaigns expect other event names.

​
Troubleshooting

Most problems are a wrong region, an API key that was replaced in Customer.io, or an event that is not ticked on the connection. When you change the key in Zippendo, fill in Site ID and API key and pick the Data region again, because the region list does not remember an EU choice. See also Integrations troubleshooting.