Skip to content
Database ⇄ Analytics

Google Cloud Spanner to Pendo integration — real-time, two-way sync

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

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

A database holds the rows your business runs on: the users, events, orders, and records that every service reads and writes. Pendo is where people make sense of them, as dashboards, funnels, cohorts, and metrics. Moving the data from Google Cloud Spanner into Pendo 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.

Stacksync syncs Views, Databases, Tables, Rows in Google Cloud Spanner with Guide Events, Poll / NPS Responses, Features / Pages / Guides (metadata), Visitors in Pendo in real time and in both directions. Operational rows flow into Pendo as they change, so dashboards read current data with no pipeline to maintain, and the segments, cohorts, or scores Pendo computes flow back into Google Cloud Spanner, where the applications and services that read from it get them at normal query latency. Field-level mapping, schema and type translation, and conflict resolution are handled for you.

Common use cases

  • 01 Export feature, page, and guide Events out of Pendo over event-time windows into Postgres or a warehouse so product usage joins with CRM, billing, and support data in SQL.
  • 02 Pull NPS scores and poll responses into a database so voice-of-customer sits next to revenue, renewal, and churn signals for analysis.
  • 03 Push billing or entitlement changes from finance tools into Spanner tables the application reads at runtime.
  • 04 Use change streams to feed near-real-time copies of operational tables into an analytics warehouse.

Common sync patterns

Where Pendo tracks product events: behavior onto stored records

Signup, usage, and lifecycle events captured in Pendo sync into Google Cloud Spanner as rows, so applications and internal tools can read behavioral data next to the records they already keep.

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

Segments, cohorts, or scores computed in Pendo 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 Pendo as they change, so dashboards, funnels, and metrics run on current data instead of last night's extract.

What you can sync between Google Cloud Spanner and Pendo

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 Pendo objects How this pairing syncs
Interleaved tables Child rows physically co-located with parents; synced as related records. Accounts Company/workspace records that roll visitors up to an account dimension; readable via Aggregation and a write target for custom fields (plan, ARR, health) via the Metadata API. Interleaved tables is specific to Google Cloud Spanner and Accounts to Pendo — 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. Feature Events Click/interaction events on tagged features, read-only through the Aggregation API over an event-time window and joined to the Feature definitions. Secondary indexes is specific to Google Cloud Spanner and Feature Events to Pendo — each maps to any object or custom field on the other side.
Change streams Capture inserts, updates, and deletes for log-style change data capture. Page Events Page-view events for tagged pages; read-only via the Aggregation API, used for adoption and path analysis in a warehouse. Change streams is specific to Google Cloud Spanner and Page Events to Pendo — each maps to any object or custom field on the other side.
Views Read-only projections useful for shaping data before it leaves Spanner. Guide Events Guide seen/advanced/dismissed and step events for in-app walkthroughs; read-only through the Aggregation API to measure onboarding flow adoption. Views is specific to Google Cloud Spanner and Guide Events to Pendo — each maps to any object or custom field on the other side.
Databases Top-level containers that scope schema and sync configuration. Poll / NPS Responses Survey answers and NPS scores captured in-app (pollEvents / npsEvents); read-only via the Aggregation API as voice-of-customer data. Databases is specific to Google Cloud Spanner and Poll / NPS Responses to Pendo — each maps to any object or custom field on the other side.
Tables Relational tables mapped one-to-one to sync targets. Features / Pages / Guides (metadata) Definitions of tagged UI elements listed through the entity endpoints; read-only reference used to label and join the event streams. Tables is specific to Google Cloud Spanner and Features / Pages / Guides (metadata) to Pendo — each maps to any object or custom field on the other side.

How changes propagate between Google Cloud Spanner and Pendo

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 Pendo 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.

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

Pendo Google Cloud Spanner Interval-based propagation

DetectionStacksync polls Pendo for changes on an incremental schedule, reading only records changed since the previous pass. Polling - reads query the Aggregation API over event-time windows.

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.
  • Pendo: Pendo does not publish fixed numeric limits; it throttles heavy Aggregation queries with 429s and caps/paginates large responses, so wide exports are paced and time-windowed.
What ships with Google Cloud Spanner ⇄ Pendo

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

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

Real-time

Two-way sync

Changes in Google Cloud Spanner or Pendo 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 Pendo 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 Pendo record.

Observability

Monitoring

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

How the Google Cloud Spanner and Pendo 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.

Pendo

Integration surface
Pendo Engage API (REST) on app.pendo.io (US) / app.eu.pendo.io (EU), base path /api/v1/ - Aggregation API for reads and the Metadata API for writes
Authentication
Integration key sent in the x-pendo-integration-key header, generated in Subscription Settings; keys are scoped read-only or read/write, so writes require a read/write key
Change detection
Polling - reads query the Aggregation API over event-time windows; no change-data-capture feed and no data-change webhooks. Writes go through the Metadata API on demand.
Capabilities
read · write
Rate limits
Pendo does not publish fixed numeric limits; it throttles heavy Aggregation queries with 429s and caps/paginates large responses, so wide exports are paced and time-windowed.
How it works

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

    Choose tables

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

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

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