Skip to main content

Customer.io

Overview​

The Customer.io connector is currently in development.

  • Source: supports credential validation, but extraction and catalog discovery are not yet implemented.
  • Destinations (Reverse ETL): connectors are registered and support credential validation, but loading is not yet implemented.

Setup​

Customer.io region​

This connector requires a region value:

  • US
  • EU

The region controls which Customer.io API hostname is used.

Authentication​

Source authentication (App API Key)​

The source uses a Customer.io App API Key.

You’ll need:

  • Region: US or EU
  • App API Key: app_api_key

During credential validation, the connector calls the Customer.io API:

  • US: https://api.customer.io/v1/api/customers?limit=1
  • EU: https://api-eu.customer.io/v1/api/customers?limit=1

Destination authentication (Site ID + API Key)​

The reverse ETL destinations use Basic Auth with:

  • Site ID: site_id
  • API Key: api_key
  • Region: US or EU

During credential validation, the connector calls:

  • US: https://track.customer.io/api/v1/accounts/region
  • EU: https://track-eu.customer.io/api/v1/accounts/region

Configuration​

Source​

FieldTypeRequiredDescription
regionstring✅Customer.io region. Must be US or EU.
app_api_keystring✅Customer.io App API Key used for API access.

Destinations (Reverse ETL)​

Applies to both Customer.io Audiences and Customer.io Conversions API destinations.

FieldTypeRequiredDescription
regionstring✅Customer.io region. Must be US or EU.
site_idstring✅Customer.io Site ID for Basic Auth.
api_keystring✅Customer.io API Key for Basic Auth.

Streams​

Source streams​

Not yet available. The connector currently returns an empty catalog and extraction is not implemented.

Reverse ETL​

Supported destinations​

  • Customer.io Audiences (in development; loading not yet implemented)
  • Customer.io Conversions API (in development; loading not yet implemented)

Hashing and normalization​

This connector does not currently expose field-level hashing options.

Data contract​

Not yet available. Destination loading is still in development, so there is no published data contract at this time.