Get workspace region
Verify the credential workspace and appropriate Track API origin.
Connector library
Customer.io connector.
Verify Customer.io Track API workspace region, update an existing person’s custom attributes and submit deduplicated person events with managed Track credentials.
Connector download
Download Customer.io
Versioned ZIP for your CXFabric tenant.
Use this connector in a flow
- Register the ZIP in your tenant, or add a new version if the connector is already installed.
- Create or select a credential if the action requires one.
- In a Draft flow, add an available action, choose its version, connect it, and map inputs.
- Test the step and flow; review output and failures before activation.
See readme.md in the ZIP for settings and limitations.
- Version
v0.2.0.1 Choose version
- Release
- 2026-10-03
- Package
- Implemented source
- Schema credentials
- Basic auth
- Connection settings
- API Base URL
- Package size
- 8 KB
- SHA-256
05e98f346e3df0458c0b7f96041d68eea647122746a80d50576b42ce45bedda2
Version history
What's new
- v0.2.0.1Latest · 2026-10-03 · Implemented source
Improves action labels, mapping hints and connection groups while retaining the existing parameter keys, types, defaults, credentials and result contracts.
- v0.2.0.0Earlier · 2026-10-03 · Implemented source
Verify Customer.io Track API workspace region, update an existing person’s custom attributes and submit deduplicated person events with managed Track credentials.
- v0.1.1.0Earlier · 2026-10-02 · Starter scaffold
Retained immutable historical scaffold archive.
Included in this version
Included actions
Implemented in v0.2.0.1. Use a separate flow trigger; no webhook trigger is included.
Update existing person attributes
Submit custom attributes for an existing person without requesting creation.
Track person event
Submit an event with a stable deduplication ULID and explicit occurrence time.
Vendor API
API and access
Implementation considerations
- Confirm consent fields, subscription status, suppression rules, required identifiers, and workspace/account scope.
- For broad marketing APIs, start with contact CRUD, event tracking, list or segment membership, and reporting reads.
- Avoid overwriting consent, source, or attribution fields without explicit customer mapping rules.
Related connectors
More in Marketing, Analytics & Revenue APIs
Support
Need help with Customer.io?
Tell us what you need to connect or change.