Two-way sync
Changes in Amazon RDS or Iterable instantly reflect in both systems. No stale data, no manual imports.
Keep Amazon RDS 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.
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 Amazon RDS, hard to get into campaigns without manual exports.
Stacksync mirrors Commerce / Purchases, Export data, Users, Events from Iterable into Read Replicas, Stored Procedures, Databases, Schemas in Amazon RDS 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 Amazon RDS, 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.
Contacts, leads, audiences, and campaign metrics from Iterable live in Amazon RDS as ordinary tables or collections, joinable with the rest of your data and reachable without touching the vendor API.
Segments computed in Amazon RDS 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.
Opens, clicks, sends, RSVPs, or ad activity from Iterable land in Amazon RDS beside the matching customer record, ready for reporting and revenue attribution.
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.
| Amazon RDS objects | Iterable objects | How this pairing syncs | |
|---|---|---|---|
| Primary and Unique Keys Match keys for idempotent upserts. | Commerce / Purchases Purchase and cart activity tracked via /api/commerce/trackPurchase and /api/commerce/updateCart, feeding revenue attribution and abandoned-cart journeys. | Primary and Unique Keys is specific to Amazon RDS and Commerce / Purchases to Iterable — each maps to any object or custom field on the other side. | |
| Read Replicas Low-impact read endpoints often used as the source side of a sync. | 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. | Read Replicas is specific to Amazon RDS and Export data to Iterable — each maps to any object or custom field on the other side. | |
| Stored Procedures Engine-specific logic that can react to synced rows. | 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. | Stored Procedures is specific to Amazon RDS and Users to Iterable — each maps to any object or custom field on the other side. | |
| Databases Engine-level databases on the instance that scope a sync's reads and writes. | 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}. | Databases is specific to Amazon RDS and Events to Iterable — each maps to any object or custom field on the other side. | |
| Schemas Namespaces within a database used to isolate synced tables. | 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. | Schemas is specific to Amazon RDS and Campaigns to Iterable — each maps to any object or custom field on the other side. | |
| Tables The core sync target; rows map to records in connected SaaS systems. | 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. | Tables is specific to Amazon RDS and Templates to Iterable — each maps to any object or custom field on the other side. |
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.
DetectionChanges in Amazon RDS are captured at the source via change data capture — no polling loop against its API. Engine-native log-based CDC: MySQL/MariaDB binlog, PostgreSQL logical replication, SQL Server CDC.
DeliveryEach detected change is written to Iterable through its API, with automatic retries and rate-limit backoff.
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 Amazon RDS as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Amazon RDS–Iterable connection.
Changes in Amazon RDS or Iterable instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Amazon RDS or Iterable data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Amazon RDS or Iterable record.
Track your Amazon RDS ⇄ Iterable sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Amazon RDS and Iterable.
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.
Authenticate Amazon RDS 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.
Pick the Amazon RDS 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Amazon RDS and Iterable: authenticate both systems, choose the objects to sync (such as Amazon RDS's Primary and Unique Keys and Read Replicas), map fields visually, and changes propagate both ways in milliseconds — no code required.
Amazon RDS: CDC prerequisites such as binlog row format or logical replication are configured through RDS parameter groups, since superuser access is not provided. Iterable: Historical data comes from the Export API, which supports data types including emailSend, emailOpen, emailClick, emailBounce, emailComplaint, purchase, customEvent, and user, exported as JSON or CSV over a date range. Stacksync's field mapping accounts for these differences between Amazon RDS and Iterable without custom code.
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 Amazon RDS and Iterable records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Amazon RDS and Iterable connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Amazon RDS–Iterable integration in-house.
Yes — Stacksync ships production-grade connectors for both Amazon RDS and Iterable. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Amazon RDS: Engine-native log-based CDC: MySQL/MariaDB binlog, PostgreSQL logical replication, SQL Server CDC; enabled through RDS parameter groups, with polling as a fallback. On Iterable: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 414 integrations available for Amazon RDS and Iterable.