Skip to content
Data warehouse ⇄ Analytics

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

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

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

Pendo is where teams explore, visualize, and report; MotherDuck 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 Poll / NPS Responses, Features / Pages / Guides (metadata), Visitors, Accounts in Pendo with Schemas, Tables, Views, Database Shares in MotherDuck 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 MotherDuck, every copy stays consistent.

Common use cases

  • 01 Pull NPS scores and poll responses into a database so voice-of-customer sits next to revenue, renewal, and churn signals for analysis.
  • 02 Push warehouse-computed Account attributes (plan, ARR, renewal date, health score, CSM owner) onto Pendo Accounts via the Metadata API so segments and guide targeting stay current.
  • 03 Land CRM and operational database records in MotherDuck so a small team gets warehouse-style analytics without cluster management
  • 04 Sync modeled MotherDuck tables outward to operational tools for activation

Common sync patterns

Where MotherDuck holds the source tables: live data in the reporting layer

Records maintained in MotherDuck 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 MotherDuck 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 MotherDuck on a stable key, so both sides count the same population.

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

MotherDuck objects Pendo objects How this pairing syncs
Database Shares Read-only copies of a database shared with other users or teams. Page Events Page-view events for tagged pages; read-only via the Aggregation API, used for adoption and path analysis in a warehouse. Database Shares is specific to MotherDuck and Page Events to Pendo — each maps to any object or custom field on the other side.
Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. Guide Events Guide seen/advanced/dismissed and step events for in-app walkthroughs; read-only through the Aggregation API to measure onboarding flow adoption. Attached Local DuckDB Databases is specific to MotherDuck and Guide Events to Pendo — each maps to any object or custom field on the other side.
Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. 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 MotherDuck and Poll / NPS Responses to Pendo — each maps to any object or custom field on the other side.
Schemas Namespaces within a database used to organize synced tables. 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. Schemas is specific to MotherDuck and Features / Pages / Guides (metadata) to Pendo — each maps to any object or custom field on the other side.
Tables The main landing target for synced records and source for analysis. 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. Tables is specific to MotherDuck and Visitors to Pendo — each maps to any object or custom field on the other side.
Views Modeled projections used as outbound sync sources. 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. Views is specific to MotherDuck and Accounts to Pendo — each maps to any object or custom field on the other side.

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

MotherDuck Pendo Interval-based propagation

DetectionStacksync polls MotherDuck for changes on an incremental schedule, reading only records changed since the previous pass. Polling.

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

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

Rate-limit considerations

  • MotherDuck: Subject to the platform's compute and concurrency limits rather than per-request API rate 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 MotherDuck ⇄ Pendo

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the MotherDuck and Pendo connectors work

MotherDuck

Integration surface
SQL through DuckDB clients and drivers using a MotherDuck (md:) connection
Authentication
Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults
Change detection
Polling; no log-based CDC or webhook surface is exposed
Capabilities
read · write
Rate limits
Subject to the platform's compute and concurrency limits rather than per-request API rate limits
MotherDuck 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 MotherDuck 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 MotherDuck 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
    MotherDuck connected
    Pendo connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

MotherDuck 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 421 integrations available for MotherDuck and Pendo.

Popular · 7 of 421
All MotherDuck 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