Skip to content
CRM ⇄ Marketing

Clearbit to Iterable integration — real-time data sync

Keep Clearbit and Iterable 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 Clearbit and Iterable

Flow Clearbit data into Iterable in real time — no exports, no schedulers, no custom scripts.

Clearbit is a read-only source: Stacksync reads its data in real time and delivers it into Iterable, so Iterable always reflects the current state of Clearbit — without exports, scripts, or schedulers.

Clearbit owns the customer relationship and the pipeline; Iterable runs the campaigns, audiences, and outreach that fill it. The two overlap on the same people and companies — a lead in one system is a subscriber, a segment member, an event registrant, or an ad audience in the other. When that overlap is bridged by CSV exports or a nightly job, sales works from lists that no longer match reality and marketing keeps targeting people whose status has already moved on.

Common use cases

  • 01 Enrich new CRM leads with person and company attributes as they are created, keyed by email and domain.
  • 02 Append technographic fields to account records in the warehouse for ICP scoring models.
  • 03 Track product and revenue Events (custom events, trackPurchase, updateCart) into Iterable from an app or database so journeys trigger on live behavior.
  • 04 Export Iterable engagement data (emailSend, emailOpen, emailClick, emailBounce, purchase) into a warehouse for deliverability and campaign reporting.

Common sync patterns

Lead and lifecycle status agree

Status, stage, or score set in one system updates the matching record in the other, so a lead marketing is still nurturing is not worked as sales-ready, and a closed account stops receiving prospecting.

Segments and audiences follow the CRM

Where Iterable builds lists, segments, or ad audiences, membership tracks the fields and stage owned in Clearbit, so who receives a campaign reflects current pipeline reality instead of a stale export.

Where Iterable generates leads: hand-off without re-keying

New leads or responders captured in Iterable flow into Clearbit assigned and deduplicated, so nothing sits in a marketing list waiting for someone to export it.

What you can sync between Clearbit and Iterable

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.

Clearbit objects Iterable objects How this pairing syncs
Persons Individual profiles looked up by email and used to enrich contacts and leads. Templates Reusable email/SMS/push/in-app message templates with handlebars fields; read via /api/templates and per-channel get endpoints, written via /api/templates/email/upsert and the other channel upserts. Persons is specific to Clearbit and Templates to Iterable — each maps to any object or custom field on the other side.
Reveal matches IP-to-company resolutions used to identify anonymous website traffic. Lists Static subscriber lists; read via GET /api/lists and /api/lists/getUsers, with users added or removed via /api/lists/subscribe and /api/lists/unsubscribe to control who receives a send. Reveal matches is specific to Clearbit and Lists to Iterable — each maps to any object or custom field on the other side.
Name-to-domain lookups Company name resolution used to normalize account records before enrichment. Catalogs Named catalogs of items (products, content) used for personalization and recommendations; items upserted and read via /api/catalogs/{catalogName}/items. Name-to-domain lookups is specific to Clearbit and Catalogs to Iterable — each maps to any object or custom field on the other side.
Enrichment attributes The firmographic and technographic fields appended to destination records. Commerce / Purchases Purchase and cart activity tracked via /api/commerce/trackPurchase and /api/commerce/updateCart, feeding revenue attribution and abandoned-cart journeys. Enrichment attributes is specific to Clearbit and Commerce / Purchases to Iterable — each maps to any object or custom field on the other side.
Companies Firmographic profiles looked up by domain and merged into account records. Export data Historical user and event records pulled through the Export API (/api/export/data.json, data.csv, and userEvents) across data types like emailSend, emailOpen, emailClick, emailBounce, purchase, and customEvent. Companies is specific to Clearbit and Export data to Iterable — each maps to any object or custom field on the other side.

How changes propagate between Clearbit and Iterable

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.

Clearbit Iterable Sub-second propagation

DetectionClearbit notifies Stacksync of record changes through webhook events. On-demand lookups.

DeliveryEach detected change is written to Iterable through its API, with automatic retries and rate-limit backoff.

Iterable Clearbit Sub-second propagation

DetectionIterable notifies Stacksync of record changes through webhook events. System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time.

DeliveryClearbit does not accept inbound record writes, so this direction carries requests rather than records: Clearbit's output flows back as field updates on the originating Iterable records.

Rate-limit considerations

  • Clearbit: Subject to plan-based API rate limits and lookup volumes.
  • Iterable: Limits are per endpoint and per project/key; exceeding one returns HTTP 429, so exponential backoff is advised. Event tracking allows far higher volume than metadata endpoints like campaigns/templates, and the Export API is throttled more tightly. Since Nov 10, 2025, passing the key in the query string or body is rate-limited more strictly than the Api-Key header.
What ships with Clearbit ⇄ Iterable

Connect Clearbit and Iterable for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Clearbit–Iterable connection.

Real-time

Real-time sync

Changes in Clearbit or Iterable instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Clearbit or Iterable 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 Clearbit or Iterable record.

Observability

Monitoring

Track your Clearbit ⇄ Iterable sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Clearbit and Iterable.

How the Clearbit and Iterable connectors work

Clearbit

Integration surface
REST API (separate endpoints per product: Enrichment, Reveal)
Authentication
API key (bearer secret key)
Change detection
On-demand lookups; asynchronous enrichment results can be delivered via webhook callbacks
Capabilities
read · webhooks
Rate limits
Subject to plan-based API rate limits and lookup volumes

Iterable

Integration surface
Iterable REST API (JSON over HTTPS): Users, Events, Campaigns, Templates, Lists, Catalogs, and Commerce endpoints, plus a bulk Export API for historical data
Authentication
API key sent in the Api-Key HTTP header (also accepted as Api_Key; the name is case-insensitive). Keys are scoped by type - Server-side, JavaScript (Web SDK), or Mobile - with optional JWT-enabled keys. US projects use api.iterable.com; EU projects use api.eu.iterable.com.
Change detection
System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time; historical backfill and incremental catch-up run through the Export API over a date range.
Capabilities
read · write · webhooks
Rate limits
Limits are per endpoint and per project/key; exceeding one returns HTTP 429, so exponential backoff is advised. Event tracking allows far higher volume than metadata endpoints like campaigns/templates, and the Export API is throttled more tightly. Since Nov 10, 2025, passing the key in the query string or body is rate-limited more strictly than the Api-Key header.
How it works

How to connect Clearbit to Iterable — 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.

  1. 01

    Connect your apps

    Authenticate Clearbit and Iterable with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Clearbit connected
    Iterable connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Clearbit and Iterable 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Clearbit ⇄ Iterable
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Clearbit Iterable
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Clearbit and Iterable integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 343 integrations available for Clearbit and Iterable.

Popular · 8 of 343
All Clearbit integrations All Iterable integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own