Skip to main content
Configview reads your Customer.io workspace (the marketing automation platform that sends your campaigns, newsletters and transactional email) through the Customer.io App API (https://api.customer.io/v1, or https://api-eu.customer.io/v1 for EU accounts), using an App API key. Configview sends only GET requests. It never sends a message, triggers a broadcast, or changes anything in Customer.io. You will end up with 1 required secret (CUSTOMERIO_APP_API_KEY) and 2 optional secrets (CUSTOMERIO_REGION and CUSTOMERIO_AUDIT_LOG_KEY) in Configview when setup is complete.
Scope of this integration today. Configview answers “how is our messaging platform run and who changed it”: workspaces (with people and message counts only), campaigns, broadcasts, newsletters and transactional messages (name, type, state, dates), segments by size, sender identities by domain, reporting webhooks by host and event names, data exports (who created each and how often it was downloaded), and the workspace and account audit logs of admin actions. It does not read people, profiles, attributes, activity, message content, templates or segment members. Customer.io has no public endpoint that lists team members or API keys, so those appear only as events in the account audit log.

What you need

  • A Customer.io account and an administrator who can create API credentials
  • An App API key for each workspace you want to collect (one key covers one workspace)
  • Optional, for team member, API key and SSO changes: an Audit Log key, which an account admin creates (it keeps working only while its creator remains an account admin)

Step 1: Open the Customer.io page in Configview

Open Configview in a second browser tab and leave it open: https://{companyname}.configview.com/admin/integrations/customer-io

Step 2: Create the App API key

  1. In Customer.io open Settings > Workspace Settings > API Credentials > App API Keys and create a key in the workspace to collect
  2. Customer.io keys do not have per-endpoint scopes. Configview needs the list endpoints only, and only ever reads.
  3. In the Configview tab paste it into CUSTOMERIO_APP_API_KEY under Credentials
  4. If your account is hosted in the EU data center, also set CUSTOMERIO_REGION to eu. Leave it empty or us otherwise. The same key does not work on the other region.
  5. Optional, for the account audit log: paste the Audit Log key into CUSTOMERIO_AUDIT_LOG_KEY. Without it the account audit log collector is skipped and everything else still runs.
Save the secrets.

Step 3: Connect and verify

  1. Click Connect. Configview creates its tables and schedules every collector at your default run time:
  1. Click Verify now. The health check reads the secrets, then lists workspaces.
If a check fails:
  • 401. The key is wrong, revoked or belongs to the other region.
  • 403. The key cannot read that area (expected for the account audit log without an Audit Log key).

Data Tables

Each table has a run_at column and keeps only the newest run.

Things worth knowing

One key, one workspace. Customer.io describes App API keys as belonging to a workspace. To cover several workspaces, run a separate Configview connection per workspace key. Whether the workspaces list returns only the key’s own workspace is not documented. Segments are counted, never listed. Configview asks Customer.io only for the number of people in each segment. Segment conditions and members are never read. Audit actors. The audit endpoints return user ids and a side list of users. Configview resolves the team member’s work email and any service account name from that list. The before and after values of a change are never read, because they can contain message content. Rate limit. Customer.io allows about 10 requests per second on most App API endpoints. Configview paces itself at 300 requests a minute and waits as long as Customer.io asks on HTTP 429. Segment sizes need one request per segment.

Known gaps

  • No team member list or API key list (Customer.io exposes neither); only audit events
  • No delivery metrics: Customer.io has no workspace-level daily aggregate, only per-campaign series, which Configview does not collect. Messages sent per workspace is tracked over time from the workspaces table.
  • Collections, snippets, assets and objects are not collected

What isn’t collected

  • People, profiles, attributes, activities, deliveries and their email addresses
  • Message and template content, campaign actions, subject lines
  • Segment conditions and members, export files and download links
  • Sender mailbox addresses and phone numbers (domain only), webhook URL paths
  • API keys and tokens