Real-time
Two-way sync
Changes in Customer.io or Salesforce instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ CRM
Customer.io to Salesforce integration — real-time, two-way sync
Keep Customer.io and Salesforce 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 Salesforce
Sync what happens in Customer.io with the customer records in Salesforce, in real time and in both directions.
The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Customer.io holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.
Stacksync connects People, Objects, Events, Segments in Customer.io to Custom Objects, Accounts, Contacts, Leads in Salesforce with bi-directional, real-time sync. Activity and record changes in Customer.io update the matching contact or account in Salesforce, and CRM data flows the other way wherever Customer.io can store and use it.
Common use cases
- 01 Keep unsubscribe and subscription-preference state consistent between Customer.io and the CRM to avoid compliance gaps.
- 02 Sync account-level objects and their person relationships for B2B messaging keyed to company attributes.
- 03 Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
- 04 Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.
Common sync patterns
Where Customer.io runs outreach
Prospects, sends, and replies sync into Salesforce, keeping lead status current without manual imports.
Where Customer.io supplies contact or company data
Enriched fields land directly on records in Salesforce, and refreshes keep them from going stale.
Where Customer.io processes payments
Charges, refunds, and subscription changes appear on the account in Salesforce, so revenue context lives with the relationship.
What you can sync between Customer.io and Salesforce
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 | Salesforce objects | How this pairing syncs | |
|---|---|---|---|
| Campaigns Automated workflows whose membership and metrics can be read via the App API. | Campaigns Marketing membership data; read out for attribution analysis in the warehouse. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Deliveries / Messages Per-recipient message records whose lifecycle events flow out through reporting webhooks. | Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. | Deliveries / Messages is specific to Customer.io and Leads to Salesforce — each maps to any object or custom field on the other side. | |
| Newsletters Recurring email sends with performance metrics available for reporting syncs. | Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. | Newsletters is specific to Customer.io and Opportunities to Salesforce — 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. | Cases Support records; synced with help desk tools or internal databases for escalation workflows. | People is specific to Customer.io and Cases to Salesforce — 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. | Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. | Objects is specific to Customer.io and Tasks and Events to Salesforce — each maps to any object or custom field on the other side. | |
| Events Behavioral events sent via the Track API that trigger campaigns. | Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. | Events is specific to Customer.io and Products and Price Books to Salesforce — each maps to any object or custom field on the other side. |
How changes propagate between Customer.io and Salesforce
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 Salesforce 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 Salesforce through its API, with automatic retries and rate-limit backoff.
Salesforce Customer.io Sub-second propagation
DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).
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.
- Salesforce: Daily API request allocations vary by edition and license count.
What ships with Customer.io ⇄ Salesforce
Connect Customer.io and Salesforce for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Customer.io–Salesforce connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Customer.io or Salesforce 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 Salesforce record.
Observability
Monitoring
Track your Customer.io ⇄ Salesforce 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 Salesforce.
How the Customer.io and Salesforce 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
Salesforce
- Integration surface
- REST, SOAP, and Bulk APIs
- Authentication
- OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
- Change detection
- Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
- Capabilities
- read · write · CDC
- Rate limits
- Daily API request allocations vary by edition and license count.
How it works
How to connect Customer.io to Salesforce — 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 Salesforce 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
Salesforce
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Customer.io and Salesforce 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 ⇄ SalesforceCustomers 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 SalesforceCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Customer.io and Salesforce integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Customer.io and Salesforce: authenticate both systems, choose the objects to sync (such as Customer.io's Campaigns and Deliveries / Messages), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Customer.io and Salesforce records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Customer.io and Salesforce connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Customer.io–Salesforce integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Customer.io and Salesforce. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Customer.io: Reporting webhooks push message and delivery events; person attribute changes are not streamed and require source-side detection. On Salesforce: Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Customer.io side: People, Objects, Events, Segments, plus custom fields where Customer.io exposes them. On the Salesforce side: Custom Objects, Accounts, Contacts, Leads. Stacksync auto-detects both schemas and converts types between the two systems.
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 448 integrations available for Customer.io and Salesforce.
Popular · 5 of 448
-
Customer.io ⇄ Copper CRM -
Salesforce ⇄ SendGrid -
Salesforce ⇄ Twilio -
Salesforce ⇄ GitHub -
Salesforce ⇄ Atlassian
No integrations match .
