Skip to content
Analytics ⇄ Data warehouse

Pendo to Starburst Enterprise integration — real-time, two-way sync

Keep Pendo and Starburst Enterprise 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 Pendo and Starburst Enterprise

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

Pendo is where teams explore, visualize, and report; Starburst Enterprise 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 Materialized views, Columns, Catalogs, Schemas in Starburst Enterprise 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 Starburst Enterprise, 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 Read federated views that join warehouse, lake, and database tables, then sync the result into operational tools like a CRM
  • 04 Expose Iceberg or Hive lake tables to sync jobs through one SQL endpoint without moving the data first

Common sync patterns

One number both sides agree on

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

Where Starburst Enterprise holds the source tables: live data in the reporting layer

Records maintained in Starburst Enterprise flow into Pendo as they change, so dashboards and reports read current rows rather than an overnight extract.

Where Pendo produces segments or scores: results back to the warehouse

Cohorts, segments, and computed metrics defined in Pendo write to Starburst Enterprise as tables the rest of the stack can query and join.

What you can sync between Pendo and Starburst Enterprise

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.

Pendo objects Starburst Enterprise objects How this pairing syncs
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 Queryable relations; writes pass through to sources whose connectors support them. Features / Pages / Guides (metadata) is specific to Pendo and Tables to Starburst Enterprise — each maps to any object or custom field on the other side.
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. Views Engine-level SQL views used to shape federated data before syncing it out. Visitors is specific to Pendo and Views to Starburst Enterprise — each maps to any object or custom field on the other side.
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. Materialized views Precomputed results that make repeated sync reads cheaper. Accounts is specific to Pendo and Materialized views to Starburst Enterprise — each maps to any object or custom field on the other side.
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. Columns Typed per the Trino type system, mapped from each source's native types. Feature Events is specific to Pendo and Columns to Starburst Enterprise — each maps to any object or custom field on the other side.
Page Events Page-view events for tagged pages; read-only via the Aggregation API, used for adoption and path analysis in a warehouse. Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. Page Events is specific to Pendo and Catalogs to Starburst Enterprise — each maps to any object or custom field on the other side.
Guide Events Guide seen/advanced/dismissed and step events for in-app walkthroughs; read-only through the Aggregation API to measure onboarding flow adoption. Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. Guide Events is specific to Pendo and Schemas to Starburst Enterprise — each maps to any object or custom field on the other side.

How changes propagate between Pendo and Starburst Enterprise

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.

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

Starburst Enterprise Pendo Interval-based propagation

DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling.

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

Rate-limit considerations

  • 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.
  • Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
What ships with Pendo ⇄ Starburst Enterprise

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Pendo and Starburst Enterprise connectors work

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.

Starburst Enterprise

Integration surface
ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
Authentication
Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
Change detection
Query-based polling; Starburst is a query engine and exposes no change log of its own
Capabilities
read · write
Rate limits
Throughput is governed by cluster sizing and resource groups rather than API quotas
How it works

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

    Choose tables

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

Pendo and Starburst Enterprise 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 408 integrations available for Pendo and Starburst Enterprise.

Popular · 7 of 408
All Pendo integrations All Starburst Enterprise 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