Skip to content
Marketing ⇄ Database

Iterable to Scaleway Postgres integration — real-time, two-way sync

Keep Iterable and Scaleway Postgres 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 Iterable and Scaleway Postgres

Give your team Iterable's contacts, campaigns, and engagement in Scaleway Postgres: query them with SQL, push audiences built from your own data back to Iterable, and skip the marketing API.

Iterable holds the people, audiences, and campaign activity that marketing runs on, but that data sits behind interfaces built for marketers, not for your internal systems. Engineers and analysts who need contacts, list membership, or engagement, for reporting, attribution, or product logic, end up writing integration code against a rate-limited API and maintaining it forever. Meanwhile the customer and usage data marketers want for targeting already lives in Scaleway Postgres, hard to get into campaigns without manual exports.

Stacksync mirrors Commerce / Purchases, Export data, Users, Events from Iterable into Schemas, Sequences, Columns, Tables in Scaleway Postgres field by field, in real time, and in both directions. Marketing records become rows your code can query and join with product and customer data; audiences and attributes computed in Scaleway Postgres, from usage, orders, or account status, sync back into Iterable to drive campaigns and ads, with Iterable kept authoritative for engagement. You decide which side owns which fields, and Stacksync resolves conflicts by rules you set.

Common use cases

  • 01 Back internal tools with the same Postgres instance while Stacksync keeps it consistent with external systems
  • 02 Keep an EU-hosted Postgres as the system of record while distributing data to US-hosted SaaS applications
  • 03 Export Iterable engagement data (emailSend, emailOpen, emailClick, emailBounce, purchase) into a warehouse for deliverability and campaign reporting.
  • 04 Stream Iterable System Webhook events into a database in near real time so opens, clicks, bounces, and unsubscribes land alongside CRM contact records.

Common sync patterns

Query Iterable like a database

Contacts, leads, audiences, and campaign metrics from Iterable live in Scaleway Postgres as ordinary tables or collections, joinable with the rest of your data and reachable without touching the vendor API.

Build audiences from your own data

Segments computed in Scaleway Postgres from product usage, orders, or account status sync into Iterable as lists or audiences, so campaigns and ads target the people your data says they should.

Engagement and results next to the customer

Opens, clicks, sends, RSVPs, or ad activity from Iterable land in Scaleway Postgres beside the matching customer record, ready for reporting and revenue attribution.

What you can sync between Iterable and Scaleway Postgres

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.

Iterable objects Scaleway Postgres objects How this pairing syncs
Catalogs Named catalogs of items (products, content) used for personalization and recommendations; items upserted and read via /api/catalogs/{catalogName}/items. Materialized views Precomputed result sets that can be read on a schedule for downstream syncs. Catalogs is specific to Iterable and Materialized views to Scaleway Postgres — each maps to any object or custom field on the other side.
Commerce / Purchases Purchase and cart activity tracked via /api/commerce/trackPurchase and /api/commerce/updateCart, feeding revenue attribution and abandoned-cart journeys. Schemas Namespace tables so multiple applications or environments can be synced selectively. Commerce / Purchases is specific to Iterable and Schemas to Scaleway Postgres — each maps to any object or custom field on the other side.
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. Sequences Generate primary keys; sync tooling must respect them when writing rows. Export data is specific to Iterable and Sequences to Scaleway Postgres — each maps to any object or custom field on the other side.
Users User profiles keyed by email or userId with custom data fields; upserted via POST /api/users/update, read via GET /api/users/{email} or getByUserId, bulk-written via /api/users/bulkUpdate (up to 1000 users per call), and deleted or GDPR-forgotten. Columns Postgres-native types, including JSONB and arrays, are mapped to fields in the paired system. Users is specific to Iterable and Columns to Scaleway Postgres — each maps to any object or custom field on the other side.
Events Custom and system events tracked via /api/events/track and /api/events/trackBulk (up to 1000 events per call); a single user's event history is read via GET /api/events/{email}. Tables Primary sync unit; each table maps to an object or table on the other side of the sync. Events is specific to Iterable and Tables to Scaleway Postgres — each maps to any object or custom field on the other side.
Campaigns Email, SMS, push, and in-app sends; metadata and metrics read via GET /api/campaigns and /api/campaigns/metrics, created and sent via /api/campaigns/create and /api/campaigns/trigger. Views Read-only sources for shaping data before it leaves the database. Campaigns is specific to Iterable and Views to Scaleway Postgres — each maps to any object or custom field on the other side.

How changes propagate between Iterable and Scaleway Postgres

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.

Iterable Scaleway Postgres 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.

DeliveryEach detected change is applied to Scaleway Postgres as a row-level write, with types converted between the two schemas.

Scaleway Postgres Iterable Sub-second propagation

DetectionChanges in Scaleway Postgres are captured at the source via change data capture — no polling loop against its API. Log-based CDC via PostgreSQL logical replication where the managed instance permits it.

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

Rate-limit considerations

  • 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.
  • Scaleway Postgres: Throughput is bounded by instance size and connection limits rather than API quotas.
What ships with Iterable ⇄ Scaleway Postgres

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Iterable and Scaleway Postgres connectors work

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.

Scaleway Postgres

Integration surface
SQL wire protocol (PostgreSQL)
Authentication
Database credentials (username/password over TLS)
Change detection
Log-based CDC via PostgreSQL logical replication where the managed instance permits it; otherwise timestamp or query-based polling
Capabilities
read · write · CDC
Rate limits
Throughput is bounded by instance size and connection limits rather than API quotas
How it works

How to connect Iterable to Scaleway Postgres — 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 Iterable and Scaleway Postgres 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
    Iterable connected
    Scaleway Postgres connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Iterable and Scaleway Postgres 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 · Iterable ⇄ Scaleway Postgres
    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
    Iterable Scaleway Postgres
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Iterable and Scaleway Postgres 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 403 integrations available for Iterable and Scaleway Postgres.

Popular · 7 of 403
All Iterable integrations All Scaleway Postgres 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