Real-time
Two-way sync
Changes in Customer.io or Pigment instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Accounting and finance
Customer.io to Pigment integration — real-time, two-way sync
Keep Customer.io and Pigment in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Customer.io and Pigment
Connect the financial records in Pigment with the work happening in Customer.io, so both stay current without exports or copy-paste.
Pigment holds the financial truth: who the customers are, what they were billed, what they paid. Customer.io is where part of the day-to-day work happens, and that work often involves the same customers and transactions. Without a live connection, the two drift apart, and people end up answering questions from stale copies.
Stacksync keeps Users and permissions, Applications, Metrics, Dimension lists in Pigment and Newsletters, People, Objects, Events in Customer.io in sync, bi-directionally and in real time. Whatever records Customer.io keeps and whatever events it produces, the overlap with Pigment is mapped field by field, and a change on either side shows up on the other within seconds.
There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning running on yesterday's data.
Common use cases
- 01 Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
- 02 Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
- 03 Sync account-level objects and their person relationships for B2B messaging keyed to company attributes.
- 04 Sync product usage and billing attributes from Postgres onto Customer.io people so lifecycle campaigns trigger on real product behavior.
Common sync patterns
Where Customer.io collects payments or triggers charges: events land in Pigment
Payment and charge activity flows into Pigment as it happens, so the books reflect reality without manual reconciliation.
Where Customer.io tracks people or companies: one identity
A customer's details updated in either system update the other, so finance and the rest of the business stop maintaining two versions of the same customer.
Where Customer.io handles customer conversations: billing context in view
Front-line teams see invoice and payment status from Pigment next to the customer they are helping, without logging into the finance system.
What you can sync between Customer.io and Pigment
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Customer.io objects | Pigment objects | How this pairing syncs | |
|---|---|---|---|
| Newsletters Recurring email sends with performance metrics available for reporting syncs. | Metrics Multidimensional values holding plans and actuals; the main target for inbound data | Newsletters is specific to Customer.io and Metrics to Pigment — each maps to any object or custom field on the other side. | |
| People Profiles with attributes, matched on identifiers like id or email; the main write target of data syncs. | Dimension lists Master data like accounts, products, or employees that metrics are sliced by | People is specific to Customer.io and Dimension lists to Pigment — each maps to any object or custom field on the other side. | |
| Objects Non-person entities such as accounts or companies, related to people for account-level messaging. | Tables Row-based transactional data loaded into models from source systems | Objects is specific to Customer.io and Tables to Pigment — each maps to any object or custom field on the other side. | |
| Events Behavioral events sent via the Track API that trigger campaigns. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | Events is specific to Customer.io and Scenarios to Pigment — each maps to any object or custom field on the other side. | |
| Segments Attribute- or event-based groups; data syncs feed the attributes segments evaluate. | Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | Segments is specific to Customer.io and Data imports to Pigment — each maps to any object or custom field on the other side. | |
| Campaigns Automated workflows whose membership and metrics can be read via the App API. | Users and permissions Access controls governing which model areas a sync can touch | Campaigns is specific to Customer.io and Users and permissions to Pigment — each maps to any object or custom field on the other side. |
How changes propagate between Customer.io and Pigment
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Customer.io Pigment Sub-second propagation
DetectionCustomer.io notifies Stacksync of record changes through webhook events. Reporting webhooks push message and delivery events.
DeliveryEach detected change is written to Pigment through its API, with automatic retries and rate-limit backoff.
Pigment Customer.io Interval-based propagation
DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.
DeliveryEach detected change is written to Customer.io through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Customer.io: Subject to per-API rate limits documented by Customer.io.
- Pigment: Subject to the platform's API rate limits.
What ships with Customer.io ⇄ Pigment
Connect Customer.io and Pigment for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Customer.io–Pigment connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Customer.io or Pigment data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Customer.io or Pigment record.
Observability
Monitoring
Track your Customer.io ⇄ Pigment sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Customer.io and Pigment.
How the Customer.io and Pigment connectors work
Customer.io
- Integration surface
- REST APIs split by purpose: Track API for data ingestion, App API for campaigns, people lookups, and messages
- Authentication
- Basic auth with site ID and API key for the Track API; bearer token for the App API
- Change detection
- Reporting webhooks push message and delivery events; person attribute changes are not streamed and require source-side detection
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-API rate limits documented by Customer.io
Pigment
- Integration surface
- REST-based import and export API
- Authentication
- API keys, issued separately for import and export
- Change detection
- no change feed; syncs run scheduled imports and exports
- Capabilities
- read · write
- Rate limits
- subject to the platform's API rate limits
How it works
How to connect Customer.io to Pigment — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Customer.io and Pigment with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Customer.io
connected
Pigment
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Customer.io and Pigment objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Customer.io ⇄ PigmentCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Customer.io PigmentCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Customer.io and Pigment integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Customer.io and Pigment: authenticate both systems, choose the objects to sync (such as Customer.io's Newsletters and People), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Customer.io: Reporting webhooks push message and delivery events; person attribute changes are not streamed and require source-side detection. On Pigment: No change feed; syncs run scheduled imports and exports. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Pigment side: Users and permissions, Applications, Metrics, Dimension lists, plus custom fields where Pigment exposes them. On the Customer.io side: Newsletters, People, Objects, Events. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Customer.io and Pigment: Where Customer.io collects payments or triggers charges: events land in Pigment; Where Customer.io tracks people or companies: one identity; Where Customer.io handles customer conversations: billing context in view. Payment and charge activity flows into Pigment as it happens, so the books reflect reality without manual reconciliation.
-
Customer.io: REST APIs split by purpose: Track API for data ingestion, App API for campaigns, people lookups, and messages. Authentication: Basic auth with site ID and API key for the Track API; bearer token for the App API. Pigment: REST-based import and export API. Authentication: API keys, issued separately for import and export. Stacksync manages authentication, retries, and rate limits on both sides.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 322 integrations available for Customer.io and Pigment.
Popular · 8 of 322
-
Customer.io ⇄ Navan -
Customer.io ⇄ Ramp -
Customer.io ⇄ Recurly -
Customer.io ⇄ Rillet -
Pigment ⇄ Wrike -
Pigment ⇄ Zendesk -
Pigment ⇄ Campfire -
Pigment ⇄ Front
No integrations match .
