Skip to content
Data warehouse ⇄ Analytics

BigQuery to Pendo integration — real-time, two-way sync

Keep BigQuery 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 BigQuery and Pendo

Put the same events, users, and metrics on both sides: Pendo and BigQuery stay current in real time, in both directions.

Pendo is where teams explore, visualize, and report; BigQuery is the store of record that holds the raw tables and full history behind those views. The two overlap wherever the same events, users, and metrics matter to both, and when the bridge between them is a nightly export or a hand-built extract, dashboards lag the warehouse and analysts spend the morning arguing over whose number is right.

Stacksync syncs Page Events, Guide Events, Poll / NPS Responses, Features / Pages / Guides (metadata) in Pendo with Partitioned tables, Clustered tables, Datasets, Projects in BigQuery field by field, in real time, and in both directions. You decide which system owns which fields, and Stacksync resolves conflicts by rules you set. Whether the flow is warehouse tables feeding live reports or captured events and segments landing back in BigQuery, every copy stays consistent.

Common use cases

  • 01 Sync Pendo Visitors and Accounts into a data model to score product-qualified accounts alongside behavioral event data.
  • 02 Load guide-engagement events into a reporting database to measure onboarding-flow adoption against retention and expansion.
  • 03 Land CRM and ERP records in BigQuery continuously so dashboards reflect business systems without nightly batch jobs
  • 04 Activate modeled BigQuery tables by syncing computed attributes back into sales and marketing tools

Common sync patterns

Shared user and account keys

Users and accounts tracked in Pendo line up with the customer or user rows in BigQuery on a stable key, so both sides count the same population.

Corrections propagate instead of reloading

When a record is fixed or backfilled on one side, the change reaches the other without a full reload, keeping history consistent across both.

One number both sides agree on

Metrics and aggregates stay aligned between the two systems, so a figure shown in Pendo matches the BigQuery table it was built from instead of drifting between refreshes.

What you can sync between BigQuery 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.

BigQuery objects Pendo objects How this pairing syncs
Partitioned tables Synced like regular tables; partition columns map to target fields. Guide Events Guide seen/advanced/dismissed and step events for in-app walkthroughs; read-only through the Aggregation API to measure onboarding flow adoption. Partitioned tables is specific to BigQuery and Guide Events to Pendo — each maps to any object or custom field on the other side.
Clustered tables Supported; clustering is transparent to the sync. Poll / NPS Responses Survey answers and NPS scores captured in-app (pollEvents / npsEvents); read-only via the Aggregation API as voice-of-customer data. Clustered tables is specific to BigQuery and Poll / NPS Responses to Pendo — each maps to any object or custom field on the other side.
Datasets Organizational container — you pick which dataset’s tables to sync. 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. Datasets is specific to BigQuery and Features / Pages / Guides (metadata) to Pendo — each maps to any object or custom field on the other side.
Projects Connection scope: the service account grants access per project. Visitors End-user records with agent-collected and custom fields; queried through the Aggregation API and enriched with custom fields written back via the Metadata API. Projects is specific to BigQuery and Visitors to Pendo — each maps to any object or custom field on the other side.
Tables The syncable unit: only tables can be synced per the Stacksync docs. 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. Tables is specific to BigQuery and Accounts to Pendo — each maps to any object or custom field on the other side.

How changes propagate between BigQuery 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.

BigQuery Pendo Sub-second propagation

DetectionChanges in BigQuery are captured at the source via change data capture — no polling loop against its API. Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen").

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

Pendo BigQuery 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 BigQuery as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • BigQuery: Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes.
  • 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 BigQuery ⇄ Pendo

Connect BigQuery and Pendo for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in BigQuery or Pendo instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever BigQuery 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 BigQuery or Pendo record.

Observability

Monitoring

Track your BigQuery ⇄ Pendo sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between BigQuery and Pendo.

How the BigQuery and Pendo connectors work

BigQuery

Integration surface
GoogleSQL via the BigQuery REST API, client libraries, JDBC/ODBC drivers, and the Storage Read/Write APIs
Authentication
Google Cloud service account: create a dedicated service account, grant roles (BigQuery Data Editor, BigQuery Job User, Cloud Functions Service Agent, Cloud Run Developer, Eventarc Event Receiver
Change detection
Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen") with a Cloud Run "secure portal for real-time notification service in
Capabilities
read · write · CDC
Rate limits
Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes
BigQuery setup guide

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 BigQuery 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 BigQuery 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
    BigQuery connected
    Pendo connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

BigQuery 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 514 integrations available for BigQuery and Pendo.

Popular · 8 of 514
All BigQuery 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