Real-time
Two-way sync
Changes in Citus or Pendo instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Analytics
Citus to Pendo integration — real-time, two-way sync
Keep Citus 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 Citus and Pendo
Give Pendo the users, events, and records that live in Citus in real time, and sync the cohorts and scores Pendo computes back into Citus 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 Citus 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 Distributed tables, Reference tables, Local tables, Schemas in Citus with Features / Pages / Guides (metadata), Visitors, Accounts, Feature Events 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 Citus, 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 Sync high-volume event or tenant data from a Citus cluster into a warehouse for cross-tenant analytics.
- 04 Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
Common sync patterns
Where Pendo builds cohorts or scores: results your services can read
Segments, cohorts, or scores computed in Pendo sync back into Citus, 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 Citus land in Pendo as they change, so dashboards, funnels, and metrics run on current data instead of last night's extract.
One version of each user or account
A user, account, or record corrected in either system updates the other, so the identity your reports group by matches the identity your database stores.
What you can sync between Citus 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.
| Citus objects | Pendo objects | How this pairing syncs | |
|---|---|---|---|
| Views Curated projections over distributed data, often used as read-only sync sources. | 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 Citus and Guide Events to Pendo — each maps to any object or custom field on the other side. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | Poll / NPS Responses Survey answers and NPS scores captured in-app (pollEvents / npsEvents); read-only via the Aggregation API as voice-of-customer data. | Sequences is specific to Citus and Poll / NPS Responses to Pendo — each maps to any object or custom field on the other side. | |
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | 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. | Distributed tables is specific to Citus and Features / Pages / Guides (metadata) to Pendo — each maps to any object or custom field on the other side. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | 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. | Reference tables is specific to Citus and Visitors to Pendo — each maps to any object or custom field on the other side. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | 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. | Local tables is specific to Citus and Accounts to Pendo — each maps to any object or custom field on the other side. | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | 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. | Schemas is specific to Citus and Feature Events to Pendo — each maps to any object or custom field on the other side. |
How changes propagate between Citus 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.
Citus Pendo Sub-second propagation
DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.
DeliveryEach detected change is written to Pendo through its API, with automatic retries and rate-limit backoff.
Pendo Citus 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 Citus as a row-level write, with types converted between the two schemas.
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.
What ships with Citus ⇄ Pendo
Connect Citus and Pendo for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Pendo connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus 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 Citus or Pendo record.
Observability
Monitoring
Track your Citus ⇄ Pendo sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Citus and Pendo.
How the Citus and Pendo connectors work
Citus
- Integration surface
- PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
- Authentication
- Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
- Change detection
- PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
- Capabilities
- read · write · CDC
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 Citus 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.
- 01
Connect your apps
Authenticate Citus 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.
Citus
connected
Pendo
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus 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.
objects · Citus ⇄ PendoCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Citus PendoCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and Pendo integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and Pendo: authenticate both systems, choose the objects to sync (such as Citus's Views and Sequences), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Citus and Pendo: Where Pendo builds cohorts or scores: results your services can read; Analytics on live operational data, minus the pipeline; One version of each user or account. Segments, cohorts, or scores computed in Pendo sync back into Citus, where the services that read from the database act on them at query speed without calling the analytics API.
-
Citus: PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node. Authentication: Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options). Pendo: 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. Stacksync manages authentication, retries, and rate limits on both sides.
-
Pendo: Reads run through the Aggregation API (POST /api/v1/aggregation), a pipeline of a source plus transforms over feature/page/guide events, poll and NPS responses, visitors, and accounts; there is no CDC feed. Citus: The managed cloud offering is Azure Cosmos DB for PostgreSQL, which is Citus under a Microsoft brand. Stacksync's field mapping accounts for these differences between Citus and Pendo without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Citus and Pendo records are not retained after a sync operation.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 404 integrations available for Citus and Pendo.
Popular · 8 of 404
-
Citus ⇄ Microsoft Power Bi -
Citus ⇄ Tableau -
Citus ⇄ Adobeanalytics -
Citus ⇄ Splunk -
Pendo ⇄ TiDB -
Pendo ⇄ TimescaleDB -
Pendo ⇄ VoltDB -
Pendo ⇄ YugabyteDB
No integrations match .
