Skip to content
Data warehouse ⇄ Analytics

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

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

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

Pendo is where teams explore, visualize, and report; Exasol 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 Features / Pages / Guides (metadata), Visitors, Accounts, Feature Events in Pendo with UDF scripts, Users and roles, Schemas, Tables in Exasol 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 Exasol, every copy stays consistent.

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 Sync computed metrics or customer segments from Exasol back into a CRM for sales and marketing use (reverse ETL).
  • 04 Consolidate data from multiple operational databases into Exasol as the central analytics layer.

Common sync patterns

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

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

Shared user and account keys

Users and accounts tracked in Pendo line up with the customer or user rows in Exasol 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.

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

Exasol objects Pendo objects How this pairing syncs
Users and roles Grant read/write access for the dedicated integration account. Page Events Page-view events for tagged pages; read-only via the Aggregation API, used for adoption and path analysis in a warehouse. Users and roles is specific to Exasol and Page Events to Pendo — each maps to any object or custom field on the other side.
Schemas Namespaces that group the tables a sync reads from or writes into. 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 is specific to Exasol and Guide Events to Pendo — each maps to any object or custom field on the other side.
Tables Primary sync target; columnar relational tables written with standard SQL. Poll / NPS Responses Survey answers and NPS scores captured in-app (pollEvents / npsEvents); read-only via the Aggregation API as voice-of-customer data. Tables is specific to Exasol and Poll / NPS Responses to Pendo — each maps to any object or custom field on the other side.
Views Read-only query surfaces often used as curated sources for reverse ETL. 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. Views is specific to Exasol and Features / Pages / Guides (metadata) to Pendo — each maps to any object or custom field on the other side.
Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. 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. Virtual schemas is specific to Exasol and Visitors to Pendo — each maps to any object or custom field on the other side.
UDF scripts In-database functions that can transform synced data after load. 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. UDF scripts is specific to Exasol and Accounts to Pendo — each maps to any object or custom field on the other side.

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

Exasol Pendo Interval-based propagation

DetectionStacksync polls Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.

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

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

Rate-limit considerations

  • Exasol: No API quota; concurrency is bounded by cluster resources and session limits.
  • 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 Exasol ⇄ Pendo

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Exasol and Pendo connectors work

Exasol

Integration surface
SQL over JDBC/ODBC drivers and a WebSocket-based client protocol
Authentication
Database credentials (username and password)
Change detection
Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients
Capabilities
read · write
Rate limits
No API quota; concurrency is bounded by cluster resources and session limits

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

    Choose tables

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

Exasol 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 404 integrations available for Exasol and Pendo.

Popular · 8 of 404
All Exasol 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