Skip to content
Last updated: 2026-04-02
Guide

Customer.io integration

The Customer.io integration connects Dxtra to your Customer.io workspace, enabling automated management of customer profiles, messaging preferences, and data subject requests across your behavioural messaging campaigns.

Customer.io stores detailed customer data — profile attributes, event history, segment memberships, campaign interactions, and messaging preferences. Connecting it to Dxtra ensures this data is covered by your privacy program and that data subject requests (access, erasure, portability) can be fulfilled automatically.

What you can do

  • Access requests — Dxtra records data about Customer.io interactions as events are ingested via webhook. For access requests, Dxtra provides the collected event data; direct Customer.io profile querying is not automated.
  • Erasure requests — Automated erasure via the Customer.io API is not yet implemented. Erasure requests for Customer.io data must be completed manually through the Customer.io dashboard.
  • Consent events — Receive unsubscribe and messaging preference changes from Customer.io into Dxtra via webhook events.
  • Data discovery — Include Customer.io in your data mapping to identify what personal data is stored in your messaging platform

Prerequisites

  • An active Customer.io account
  • A Dxtra account with admin access
  • Your Customer.io App API Key and your account region (US or EU)

Setup instructions

Step 1: Get your Customer.io API credentials

  1. Log in to your Customer.io account
  2. Go to Settings > Account Settings > App API Keys
  3. Generate a new App API key with reporting webhook permissions
  4. Note your account region (US or EU)

Tip

Use a dedicated API key for the Dxtra integration rather than sharing keys with other services. This makes it easier to audit access and revoke if needed.

Step 2: Add Customer.io as a data processor

  1. In the Dxtra dashboard, go to Processors in the left sidebar
  2. In the Onboard a Data Processor section, open the Select Processor dropdown
  3. Select Customer.io from the list
  4. Review the processor details — Dxtra displays a description of Customer.io and the data processing relationship
  5. Confirm the integration to add Customer.io to your Data Processors list

Note

If Customer.io does not appear in the processor dropdown, you can add it as a custom processor using Add Processor at the bottom of the dropdown.

Step 3: Configure the connection

  1. Enter your Customer.io App API Key and select your account region (US or EU)
  2. Dxtra verifies the credentials and establishes the connection
  3. Once connected, Customer.io appears as Interconnected in your Manage Processors table

Step 4: Configure data sync

After connecting, configure what data Dxtra synchronises:

Inbound event processing — Customer.io sends webhook events to Dxtra when customer data changes. Dxtra processes these events through the PII extraction pipeline and updates data subject records accordingly.

Data mapping — Configure which Customer.io data fields are included in your data map. This helps maintain an accurate record of processing activities.

Note

Customer.io is also used as Dxtra's transactional email provider (for contact form submissions and system notifications). This integration page covers the data processor connection for privacy compliance.

Data covered by the integration

The Customer.io integration covers the following data categories:

Data category Access Erasure Notes
Customer profiles — — Names, emails, attributes, custom properties
Event history — — Behavioural events tracked in Customer.io
Segment memberships — — Which segments the customer belongs to
Campaign interactions — — Opens, clicks, conversions, deliveries
Messaging preferences — — Subscription status, channel preferences
Custom attributes — — Any custom data fields you store in Customer.io

How data subject requests work

When a data subject submits a request through the Transparency Center or you receive a request through another channel:

Access request — Dxtra provides the Customer.io event data that has been collected via webhook since the integration was connected. Direct querying of Customer.io for historical data is not automated.

Erasure request — Automated deletion via the Customer.io API is not yet implemented. Erasure requests must be fulfilled manually through the Customer.io dashboard. Dxtra will log the manual action in the Processing Activity Log when you mark the request as complete.

Portability request — Dxtra includes Customer.io event data collected via webhooks since the integration was connected. Full historical data from Customer.io must be exported manually from the Customer.io dashboard.

Troubleshooting

Connection fails — Verify that your App API Key is correct and has the necessary permissions. Customer.io App API Keys are workspace-specific — ensure you are using a key from the correct workspace.

Data subject request times out — Customer.io's API has rate limits. If you are processing a high volume of requests, some may take longer to complete. Dxtra retries failed requests automatically. Check the request status in the DSRR History panel.

Events not appearing — Verify that Customer.io webhooks are configured to send to the correct Dxtra endpoint. Check that the webhook URL includes the correct encrypted token parameter.

Customer not found — Customer.io identifies customers by their unique ID or email address. If a data subject's request uses a different identifier than what is stored in Customer.io, the lookup may fail. Verify the identity mapping in your integration settings.

Not legal advice

This documentation provides guidance on integrating Customer.io with Dxtra. AI-generated content does not constitute legal advice. Consult a qualified legal professional for advice specific to your jurisdiction and business context.