Skip to content
Database ⇄ Analytics

Google Cloud Spanner to Tableau integration — real-time data sync

Keep Google Cloud Spanner and Tableau 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 Spanner and Tableau

Give Tableau the users, events, and records that live in Google Cloud Spanner in real time, and sync the cohorts and scores Tableau computes back into Google Cloud Spanner where your applications read them.

Tableau is a read-only source: Stacksync reads its data in real time and delivers it into Google Cloud Spanner, so Google Cloud Spanner always reflects the current state of Tableau — without exports, scripts, or schedulers.

A database holds the rows your business runs on: the users, events, orders, and records that every service reads and writes. Tableau is where people make sense of them, as dashboards, funnels, cohorts, and metrics. Moving the data from Google Cloud Spanner into Tableau usually means a hand-built extract or a change-data-capture pipeline that breaks the moment a column is renamed, and reporting that always trails last night's load.

Common use cases

  • 01 Track Extract Refresh Tasks and DatasourceRefreshFailed webhook events to raise alerts in a database or ticketing system when refreshes fail.
  • 02 Read site Users and their site roles for periodic access reviews and to reconcile Tableau accounts against an HR or IdP source of record.
  • 03 Run a two-way sync between Spanner and a SaaS tool so edits made by ops teams land back in the application database.
  • 04 Consolidate data from a globally distributed Spanner deployment into regional business systems.

Common sync patterns

Where Tableau builds cohorts or scores: results your services can read

Segments, cohorts, or scores computed in Tableau sync back into Google Cloud Spanner, where the services that read from the database act on them at query speed without calling the analytics API.

Analytics on live operational data, minus the pipeline

The users, events, orders, and records stored in Google Cloud Spanner land in Tableau as they change, so dashboards, funnels, and metrics run on current data instead of last night's extract.

One version of each user or account

A user, account, or record corrected in either system updates the other, so the identity your reports group by matches the identity your database stores.

What you can sync between Google Cloud Spanner and Tableau

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 Spanner objects Tableau objects How this pairing syncs
Views Read-only projections useful for shaping data before it leaves Spanner. Views Worksheets and dashboards inside workbooks; their data and crosstab export as CSV via the REST query-view-data endpoint. Same entity on both sides — records pair one-to-one and field-level changes reconcile in the writable direction.
Databases Top-level containers that scope schema and sync configuration. Projects Folders that organize content and set permissions; listed via REST to mirror the site's content hierarchy into a catalog. Databases is specific to Google Cloud Spanner and Projects to Tableau — each maps to any object or custom field on the other side.
Tables Relational tables mapped one-to-one to sync targets. Users Site users with site roles and group membership; read via REST for access reviews and to reconcile identities against an HR or IdP source. Tables is specific to Google Cloud Spanner and Users to Tableau — each maps to any object or custom field on the other side.
Rows The unit of read and write in each sync cycle, keyed by primary key. Databases and Tables External assets indexed by Tableau Catalog; queried via the Metadata API GraphQL endpoint for lineage and impact analysis. Rows is specific to Google Cloud Spanner and Databases and Tables to Tableau — each maps to any object or custom field on the other side.
Interleaved tables Child rows physically co-located with parents; synced as related records. Extract Refresh Tasks Scheduled extract refreshes; status and history read via REST, with DatasourceRefreshSucceeded and Failed events delivered by webhooks. Interleaved tables is specific to Google Cloud Spanner and Extract Refresh Tasks to Tableau — each maps to any object or custom field on the other side.
Secondary indexes Used to make incremental read queries efficient on non-key columns. Fields and Columns Columns and calculated fields with their descriptions, exposed by the Metadata API; read to populate a data catalog with governed definitions. Secondary indexes is specific to Google Cloud Spanner and Fields and Columns to Tableau — each maps to any object or custom field on the other side.

How changes propagate between Google Cloud Spanner and Tableau

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 Spanner Tableau Sub-second propagation

DetectionChanges in Google Cloud Spanner are captured at the source via change data capture — no polling loop against its API. Change streams (log-style CDC), or timestamp-based polling queries.

DeliveryTableau does not accept inbound record writes, so this direction carries requests rather than records: Tableau's output flows back as field updates on the originating Google Cloud Spanner records.

Tableau Google Cloud Spanner Sub-second propagation

DetectionTableau notifies Stacksync of record changes through webhook events. Webhooks fire on workbook and data source create/update/delete and extract refresh events.

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

Rate-limit considerations

  • Google Cloud Spanner: Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.
  • Tableau: Tableau Cloud enforces per-site REST rate limits and returns HTTP 429; a PAT allows only one concurrent session and expires after 15 consecutive days of non-use.
What ships with Google Cloud Spanner ⇄ Tableau

Connect Google Cloud Spanner and Tableau for flexible, real-time data sync.

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Google Cloud Spanner ⇄ Tableau 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 Spanner and Tableau.

How the Google Cloud Spanner and Tableau connectors work

Google Cloud Spanner

Integration surface
gRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects)
Authentication
Google Cloud IAM (service accounts)
Change detection
Change streams (log-style CDC), or timestamp-based polling queries
Capabilities
read · write · CDC
Rate limits
Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.

Tableau

Integration surface
REST API, Metadata API (GraphQL), and VizQL Data Service
Authentication
Sign-in via Personal Access Token (PAT) or username/password returns a credentials token sent as the X-Tableau-Auth header; Connected Apps issue JWTs for OAuth-style access. One active session per PAT.
Change detection
Webhooks fire on workbook and data source create/update/delete and extract refresh events; otherwise content and metadata are polled via REST list endpoints (updatedAt) and the Metadata API.
Capabilities
read · webhooks
Rate limits
Tableau Cloud enforces per-site REST rate limits and returns HTTP 429; a PAT allows only one concurrent session and expires after 15 consecutive days of non-use.
How it works

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

    Choose tables

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

Google Cloud Spanner and Tableau 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 359 integrations available for Google Cloud Spanner and Tableau.

Popular · 7 of 359
All Google Cloud Spanner integrations All Tableau 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