Customer.io
Connect Querri to Customer.io and ask questions about your people, segments and messaging in plain language.
Overview
Section titled “Overview”The Customer.io connector uses an App API key to read your Customer.io workspace, and copies its data into Querri. Each kind of Customer.io data becomes a source in your Library. It’s listed under Marketing and Messaging.
Before you start
Section titled “Before you start”- An App API key. In Customer.io, it’s under Settings > API Credentials. The form asks specifically for an App API key.
- Your data region. Know whether your Customer.io workspace is in the EU region.
Connecting to Customer.io
Section titled “Connecting to Customer.io”-
Open the connector. Click Connect in the app rail and pick Customer.io in Add data, or click Connect on Customer.io in Settings → Connectors (admins).
-
Enter your details:
Field What to enter Default App API Key Your App API key Data Region Global (US) or European Union. Pick EU only if your workspace is in the EU region Global (US) -
Save. Click Save. There’s no separate test step: Querri checks the key with Customer.io first, and creates the connector only if it works. If it doesn’t, nothing is saved and the dialog shows the reason. When it works, the dialog closes and you’ll see “Customer.io connected”.
-
Load your data. Open the connector in the Library by clicking it under Connectors in the browse panel. If nothing has loaded yet, you’ll see “Customer.io is connected, but no data has loaded yet.” Click Load data now. Only the connector’s owner can start a load.
- App API Key: the key Querri reads your workspace with.
- Data Region: where your workspace is hosted.
What syncs
Section titled “What syncs”The first load brings in all of these:
| Area | Data | What it holds |
|---|---|---|
| People | People | Customer profiles and their attributes |
| Segments | Segment definitions and rules | |
| Messaging | Campaigns | Automated campaigns and their performance |
| Messages | Individual messages sent, with delivery status | |
| Newsletters | Newsletter campaigns and broadcast emails | |
| Broadcasts | One-time broadcast messages and their delivery data | |
| Activity | Activities | Customer activity logs, including events and actions |
Keeping data fresh
Section titled “Keeping data fresh”The connector’s owner can set a schedule on its Schedule tab. Customer.io doesn’t support incremental syncs, so use Full Refresh.
Scheduled syncs use credits when they run; syncs you start by hand don’t. See Sync Scheduling and Credits.
Troubleshooting
Section titled “Troubleshooting”The key is rejected
Section titled “The key is rejected”Check that you copied an App API key. Then check Data Region: Querri calls Customer.io’s US or EU address depending on your choice, so it has to match your workspace’s region.
Syncs take a long time
Section titled “Syncs take a long time”Customer.io limits how fast its API can be called, and Querri paces its requests to stay within that limit. Workspaces with many people or messages take longer.
Security & permissions
Section titled “Security & permissions”- An API key, not a person’s login. Querri connects with an App API key, not with anyone’s own username and password.
- Querri keeps a copy. Synced data is stored in Querri. Disconnecting deletes the data the connector synced.
- Sharing the connector is up to its owner, on the connector’s Sharing tab.
Next Steps
Section titled “Next Steps”- Sync Scheduling: full refresh schedules
- Managing Connections: change, refresh and remove connectors
- Data Connectors Overview: every connector Querri offers