Skip to content
Data warehouse ⇄ Marketing

Google Cloud Platform to Iterable integration — real-time, two-way sync

Keep Google Cloud Platform 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 Google Cloud Platform and Iterable

Put modeled data to work and measure what it drives: Google Cloud Platform and Iterable keep contacts, audiences, and campaign results in step in real time, in both directions.

Google Cloud Platform 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 Pub/Sub topics, Firestore documents, Spanner tables, BigQuery datasets in Google Cloud Platform with Events, Campaigns, Templates, Lists 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 Google Cloud Platform — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Publish change events to Pub/Sub so downstream services react to record updates as they happen.
  • 02 Write list subscribe/unsubscribe changes from a CRM back into Iterable Lists so suppression and opt-in state stay current before the next send.
  • 03 Two-way sync User profiles and their custom data fields between Iterable and a Postgres database or CRM so attributes and subscription state stay aligned in both systems.

Common sync patterns

Activate a modeled audience

A segment or score built in Google Cloud Platform — 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.

Keep the contact and audience list current

New and updated contacts, leads, or audience members flow between Google Cloud Platform and Iterable, so the marketing audience reflects the people in your warehouse and corrections propagate instead of the two sides drifting apart.

Suppression and consent stay aligned

Unsubscribes, bounces, and consent or opt-out flags held in either system propagate to the other, so no one is messaged after opting out and Google Cloud Platform holds the current state for auditing.

What you can sync between Google Cloud Platform 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.

Google Cloud Platform objects Iterable objects How this pairing syncs
Cloud Storage objects Staging area for file-based bulk loads into BigQuery and other services. 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. Cloud Storage objects is specific to Google Cloud Platform and Campaigns to Iterable — each maps to any object or custom field on the other side.
Pub/Sub topics Event streams used to move change events between systems in near real time. 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. Pub/Sub topics is specific to Google Cloud Platform and Templates to Iterable — each maps to any object or custom field on the other side.
Firestore documents Document data read and written through the Firestore API for app-facing syncs. 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. Firestore documents is specific to Google Cloud Platform and Lists to Iterable — each maps to any object or custom field on the other side.
Spanner tables Strongly consistent relational tables accessed via SQL for transactional workloads. Catalogs Named catalogs of items (products, content) used for personalization and recommendations; items upserted and read via /api/catalogs/{catalogName}/items. Spanner tables is specific to Google Cloud Platform and Catalogs to Iterable — each maps to any object or custom field on the other side.
BigQuery datasets Namespaces that group tables; syncs target tables within a dataset. Commerce / Purchases Purchase and cart activity tracked via /api/commerce/trackPurchase and /api/commerce/updateCart, feeding revenue attribution and abandoned-cart journeys. BigQuery datasets is specific to Google Cloud Platform and Commerce / Purchases to Iterable — each maps to any object or custom field on the other side.
BigQuery tables The primary analytics destination, written through load jobs or the Storage Write API and queried with SQL. 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. BigQuery tables is specific to Google Cloud Platform and Export data to Iterable — each maps to any object or custom field on the other side.

How changes propagate between Google Cloud Platform 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.

Google Cloud Platform Iterable Sub-second propagation

DetectionGoogle Cloud Platform pushes changes as they happen — webhook events backed by change data capture. Varies by service: log-based CDC on Cloud SQL (logical replication or binlog, also via Datastream), Pub/Sub for event delivery, polling for BigQuery.

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

Iterable Google Cloud Platform 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 Google Cloud Platform as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Google Cloud Platform: Quotas are set per service and per project; BigQuery, Pub/Sub, and Cloud SQL each enforce their own limits.
  • 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 Google Cloud Platform ⇄ Iterable

Connect Google Cloud Platform and Iterable for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Google Cloud Platform and Iterable.

How the Google Cloud Platform and Iterable connectors work

Google Cloud Platform

Integration surface
Per-service REST and gRPC APIs; BigQuery speaks SQL and Cloud SQL exposes standard database wire protocols
Authentication
IAM service accounts with OAuth 2.0 tokens
Change detection
Varies by service: log-based CDC on Cloud SQL (logical replication or binlog, also via Datastream), Pub/Sub for event delivery, polling for BigQuery tables
Capabilities
read · write · CDC · webhooks
Rate limits
Quotas are set per service and per project; BigQuery, Pub/Sub, and Cloud SQL each enforce their own limits

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 Google Cloud Platform 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 Google Cloud Platform 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
    Google Cloud Platform connected
    Iterable connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Google Cloud Platform 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 499 integrations available for Google Cloud Platform and Iterable.

Popular · 8 of 499
All Google Cloud Platform 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