Advanced Analytica Advanced Analytica: IBOM
← All connectors
Customer IO logo

Destination connector

Customer IO

Send governed data into Customer IO with a clear, practical setup guide.

Version 0.0.12 community alpha

Customer.io

Use this page to set up the Customer.io destination connector and find its reference information.

Overview

The Customer.io destination connector syncs data to Customer.io using the Track API v2 batch endpoint. It supports data activation, so you can identify people and track Customer.io events from your data warehouse or other sources.

Prerequisites

  • A Customer.io account
  • A Customer.io Track API Key and Site ID (see Setup guide)
  • Airbyte version 1.8 or later, or Airbyte Cloud

S3 prerequisites for rejected records

To store rejected records in an S3 bucket, you’ll also need the following.

  1. Allow connections from Airbyte to your AWS S3/Minio S3 cluster if they’re in separate VPCs.

  2. Enforce encryption of data in transit.

  3. An S3 bucket with credentials, a Role ARN, or an instance profile with host read/write permissions configured for EC2 or EKS.

    • You must always provide these fields:

      • S3 Bucket Name
      • S3 Bucket Region
      • Prefix Path in the Bucket
    • If you’re using STS Assume Role, you must provide:

      • Role ARN
    • If you’re using AWS credentials, you must provide:

      • Access Key ID
      • Secret Access Key
    • If you’re using an Instance Profile, you can omit the Access Key ID, Secret Access Key, and Role ARN.

Setup guide

Configure the connector as follows:

  1. In Customer.io, go to Settings > API & Webhook Credentials.
  2. Under Track API Keys, click Create Track API Key.
  3. Copy the Site ID and API Key.
  4. In Airbyte, create a new Customer.io destination and enter the Site ID and API Key.

The connector uses HTTP Basic authentication, with the Site ID as the username and the API Key as the password.

Rejected records

You can store rejected records in object storage, such as S3. Configure object storage in the connector settings to capture records that couldn’t sync to Customer.io. Rejections may result from payload size limits, missing required fields or Customer.io API validation errors.

Objects and operations

The connector supports two destination objects:

  • person_identify (Upsert): Identifies a person and assigns attributes to them. The person_email field is required and serves as the matching key. Every other record field is sent as a person attribute.
  • person_event (Insert): Tracks an event for a person. Required fields: person_email, event_name. Optional fields: event_id (for event deduplication), timestamp (Unix timestamp). Every other field is sent as an event attribute.

Supported sync modes

Sync modeSupported?
Full Refresh - OverwriteNo
Full Refresh - AppendYes
Full Refresh - Overwrite + DedupedNo
Incremental Sync - AppendYes
Incremental Sync - Append + DedupedNo

This is a data activation destination. Alongside the Airbyte sync modes above, Customer.io supports identify (person) and track (event) operations configured for each stream.

Limitations

  • The connector sends data to the US region endpoint (track.customer.io). For EU-region Customer.io accounts, data still reaches your workspace but first passes through US servers. See Customer.io server addresses for details.
  • The Track API limits requests to 1000 per second. The connector batches records, up to 500 KB per batch, to stay within this limit.
  • Each batch entry must be 32 KB or smaller.
  • Customer.io applies these attribute limits:
    • Maximum 300 attributes per person or identify call
    • Maximum 100 KB total attribute size per person
    • Attribute names: 150 bytes or smaller
    • Attribute values: 1000 bytes or smaller
  • Event names must be 100 bytes or smaller.

Namespace support

This destination doesn’t support namespaces.

Changelog

VersionDatePull RequestSubject
0.0.122026-10-2289652Upgrade to Bulk CDK 1.1.9: fix critical CVEs in Apache MINA (mina-core 2.0.31), MINA SSHD 2.20.0 and BouncyCastle 1.86; netty 4.1.139, Hadoop 3.4.3, Parquet 1.18.1
0.0.112026-06-1880254Move to community support level
0.0.102026-02-0972973Upgrade CDK to 1.0.1
0.0.92026-01-2672303Upgrade CDK to 0.2.0
0.0.82025-11-0569132Upgrade to Bulk CDK 0.1.61
0.0.72025-09-2366571Fix person_identify in incremental mode
0.0.62025-09-1866238Use low-code discover definition and pin to a CDK version
0.0.52025-09-0865157Update following breaking changes on spec
0.0.42025-08-2065113Update logo
0.0.32025-07-1062848Improve UX on connector configuration
0.0.22025-07-0862843Checker should validate DLQ
0.0.12025-07-0762083Initial release of the Customer.io destination connector
Advanced Analytica

Most businesses are sitting on information they can’t use at speed. The people who hold it are busy, and when they leave, the knowledge goes with them. The documents are static, and the processes around them weren’t designed for AI.

Advanced Analytica works with these businesses to turn that information into structured data assets. Once they're integrated, AI systems can govern it, and the business can use it. We bring in the strategy, the specification and the AI skills to rework how the business operates.

MOVE FAST. STAY SAFE.