Skip to content
Data warehouse ⇄ Database

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

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

Connect Reltio and Google Cloud Platform with one live, two-way sync: operational rows flow into the warehouse, and computed results flow back where systems can read them fast.

Operational databases and analytical warehouses want the same data at different moments. Analysts want Reltio's rows in Google Cloud Platform, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in Reltio where the services that read from it get them at normal query latency.

Stacksync covers both directions with one connection. Tables or collections in Reltio sync into Google Cloud Platform in real time, and result tables in Google Cloud Platform sync back into Reltio, with schema and type mapping between the two systems handled for you.

Common use cases

  • 01 Publish change events to Pub/Sub so downstream services react to record updates as they happen.
  • 02 Sync Relations (affiliations, hierarchies, households) between Reltio and a CRM or graph so account and affiliation structures stay aligned.
  • 03 Feed Interactions (transactions, visits, events) into Reltio to enrich entity profiles, then read them back for 360-degree reporting.

Common sync patterns

Serve warehouse results at database speed

Aggregates or model outputs computed in Google Cloud Platform sync into Reltio, where whatever reads from that database gets them without querying the warehouse.

Fresh analytics without loading windows

Because changes stream continuously, analysts query current data instead of waiting for last night's load.

Offload heavy reads

Point analytical queries at the synced copy in Google Cloud Platform and keep Reltio focused on its operational workload.

What you can sync between Google Cloud Platform and Reltio

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 Reltio objects How this pairing syncs
BigQuery datasets Namespaces that group tables; syncs target tables within a dataset. Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. BigQuery datasets is specific to Google Cloud Platform and Data Change Requests (DCR) to Reltio — 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. Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. BigQuery tables is specific to Google Cloud Platform and Reference Data (RDM) to Reltio — each maps to any object or custom field on the other side.
Cloud SQL databases Managed Postgres, MySQL, and SQL Server instances synced like ordinary relational databases. Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. Cloud SQL databases is specific to Google Cloud Platform and Entities to Reltio — each maps to any object or custom field on the other side.
Cloud Storage objects Staging area for file-based bulk loads into BigQuery and other services. Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. Cloud Storage objects is specific to Google Cloud Platform and Relations to Reltio — 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. Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. Pub/Sub topics is specific to Google Cloud Platform and Crosswalks to Reltio — 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. Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. Firestore documents is specific to Google Cloud Platform and Interactions to Reltio — each maps to any object or custom field on the other side.

How changes propagate between Google Cloud Platform and Reltio

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 Reltio 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 Reltio through its API, with automatic retries and rate-limit backoff.

Reltio Google Cloud Platform Interval-based propagation

DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.

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.
  • Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
What ships with Google Cloud Platform ⇄ Reltio

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

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

Real-time

Two-way sync

Changes in Google Cloud Platform or Reltio 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 Reltio 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 Reltio record.

Observability

Monitoring

Track your Google Cloud Platform ⇄ Reltio 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 Reltio.

How the Google Cloud Platform and Reltio 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

Reltio

Integration surface
Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
Authentication
OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
Change detection
Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
Capabilities
read · write
Rate limits
Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
How it works

How to connect Google Cloud Platform to Reltio — 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 Reltio 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
    Reltio connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Google Cloud Platform and Reltio 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
CSA STAR
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 464 integrations available for Google Cloud Platform and Reltio.

Popular · 6 of 464
All Google Cloud Platform integrations All Reltio 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