Two-way sync
Changes in Iterable or Teradata Vantage instantly reflect in both systems. No stale data, no manual imports.
Keep Iterable and Teradata Vantage in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Teradata Vantage is where your team models customers, product usage, and revenue into trusted tables; Iterable runs the campaigns, audiences, and messages that reach those people. The two overlap wherever the same person, account, or segment matters to both, and when the bridge between them is a nightly export or a hand-built list, marketing targets stale data while analytics never sees what the campaign returned.
Stacksync syncs Columns, Databases, Tables, Views in Teradata Vantage with Commerce / Purchases, Export data, Users, Events in Iterable field by field, in real time, and in both directions. You decide which system owns which fields — a computed score or segment can flow out to Iterable while sends, opens, and conversions flow back to Teradata Vantage — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Product-usage counts, plan tier, region, or account owner computed in Teradata Vantage appear on the matching record in Iterable, so targeting, routing, and personalization use up-to-date context.
A segment or score built in Teradata Vantage — high-intent accounts, churn risk, a lifetime-value tier — lands as an audience or contact field in Iterable, so campaigns target the people your data actually points to instead of a static export.
New and updated contacts, leads, or audience members flow between Teradata Vantage and Iterable, so the marketing audience reflects the people in your warehouse and corrections propagate instead of the two sides drifting apart.
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 | Teradata Vantage objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Users In Teradata, users are databases with a password, and they own objects and space. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| 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. | Columns Teradata SQL types mapped to the paired system's field types during sync. | Templates is specific to Iterable and Columns to Teradata Vantage — each maps to any object or custom field on the other side. | |
| 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. | Databases Hierarchical containers that own tables and space allocations. | Lists is specific to Iterable and Databases to Teradata Vantage — each maps to any object or custom field on the other side. | |
| Catalogs Named catalogs of items (products, content) used for personalization and recommendations; items upserted and read via /api/catalogs/{catalogName}/items. | Tables The primary sync unit for both extraction and loading. | Catalogs is specific to Iterable and Tables to Teradata Vantage — 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. | Views The conventional access layer in Teradata shops; syncs often read views rather than base tables. | Commerce / Purchases is specific to Iterable and Views to Teradata Vantage — 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. | Macros Stored parameterized SQL that encapsulates repeatable reads. | Export data is specific to Iterable and Macros to Teradata Vantage — 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.
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 Teradata Vantage as a row-level write, with types converted between the two schemas.
DetectionStacksync polls Teradata Vantage for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling.
DeliveryEach detected change is written to Iterable through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Iterable–Teradata Vantage connection.
Changes in Iterable or Teradata Vantage instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Iterable or Teradata Vantage data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Iterable or Teradata Vantage record.
Track your Iterable ⇄ Teradata Vantage sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Iterable and Teradata Vantage.
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 Iterable and Teradata Vantage 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 Iterable and Teradata Vantage 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 Iterable and Teradata Vantage: authenticate both systems, choose the objects to sync (such as Iterable's Users and Templates), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Iterable and Teradata Vantage: Enrich records with warehouse context; Activate a modeled audience; Keep the contact and audience list current. Product-usage counts, plan tier, region, or account owner computed in Teradata Vantage appear on the matching record in Iterable, so targeting, routing, and personalization use up-to-date context.
Iterable: 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. Teradata Vantage: ANSI SQL over JDBC/ODBC/.NET drivers; REST access available through Teradata's query service. Authentication: Database credentials; LDAP or Kerberos in enterprise deployments. Stacksync manages authentication, retries, and rate limits on both sides.
Teradata Vantage: Vantage runs on-premise and on public clouds with the same SQL engine, so integration logic carries across deployment models. Iterable: Iterable authenticates with an API key in the Api-Key header (also accepted as Api_Key; the name is case-insensitive); keys are scoped by type - Server-side, JavaScript/Web, or Mobile. Stacksync's field mapping accounts for these differences between Iterable and Teradata Vantage 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 Iterable and Teradata Vantage records are not retained after a sync operation.
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 399 integrations available for Iterable and Teradata Vantage.