Zippendo
Customer.io

Customer.io

Send shipment, order and tracking events from Zippendo to Customer.io and use them to trigger campaigns for shipping, tracking and order messages, in the US or EU region.

About Customer.io

Customer.io is a messaging platform for lifecycle and transactional messages. You send it events about your customers, and campaigns react to those events with emails, push notifications or SMS. Workspaces run in either a US or an EU data region.

Why connect Customer.io to Zippendo?

Customer.io is only as useful as the events you feed it. Your webshop sends the purchase, but the parcel's journey after that happens in Zippendo, where the shipment is created, booked with the carrier and tracked. Connect Customer.io, and those events arrive on the customer's profile in your workspace.

Shipping messages triggered by the real booking

When Zippendo books a shipment with the carrier, Customer.io receives a shipment.dispatched event. Use it as the trigger for a campaign that tells the customer the order is on its way, with the tracking number and carrier from the event data.

Tracking updates in your own channels

Every new status the carrier reports becomes a tracking.updated event with the tracking number, carrier and status. Filter on the status in your campaign and send a push or SMS when the parcel is out for delivery or ready for pickup.

Order events for the rest of your lifecycle

order.created, order.updated and shipment.cancelled give your campaigns the order side too, wherever the order came from, so cancellation notices and order follow-ups run from the same workspace.

Filter and delay with automations

Want Customer.io to hear only about some shipments? Build an automation in Zippendo with a trigger, a condition on any field, an optional delay and the Send Customer.io Event action, with your own event name and extra properties.

What you can do with Customer.io and Zippendo

  • shipment.created: a shipment was created in Zippendo
  • shipment.dispatched: the shipment was booked with the carrier and has a label
  • shipment.cancelled: the shipment was cancelled
  • order.created and order.updated: an order came in or was changed
  • tracking.updated: the carrier reported a new tracking status
  • Event data: the event's full data plus source: zippendo, tracked against the customer's email when the event carries it
  • Your own event names: override the name per event on the connection, or per action in an automation
  • US or EU region: choose the data region your Customer.io workspace runs in
  • Test event and delivery log: send a test from the connection card and see every attempt and Customer.io's response

How do I connect Customer.io?

The events come from your shipping, so connect your shop and a carrier first. Zippendo has ready-made integrations for Shopify and WooCommerce, and other systems can send orders through the API. Your shipping rules then book orders with carriers like GLS, PostNord or Bring. Customer.io can run next to other apps such as Slack or Make; see all integrations.

In Zippendo, open Apps & integrations, find Customer.io in the catalog and click Connect. You need the Site ID and API key from Customer.io's API credentials, and you choose the data region, US or EU. Pick the region your workspace actually runs in: the wrong one makes authentication fail. Choose the events to send automatically, save, and send a test event. The Customer.io setup guide in our docs covers each step.

Customer.io integration FAQ

Start automating with Customer.io

Connect your Customer.io workspace, pick the events you want, and trigger your first shipping campaign on shipment.dispatched.