Two-way sync
Changes in OCI Database (Oracle Cloud) or Pendo instantly reflect in both systems. No stale data, no manual imports.
Keep OCI Database (Oracle Cloud) 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.
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 OCI Database (Oracle Cloud) 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 Tables, Views, Materialized views, Schemas in OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud), 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.
Segments, cohorts, or scores computed in Pendo sync back into OCI Database (Oracle Cloud), where the services that read from the database act on them at query speed without calling the analytics API.
The users, events, orders, and records stored in OCI Database (Oracle Cloud) land in Pendo as they change, so dashboards, funnels, and metrics run on current data instead of last night's extract.
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.
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.
| OCI Database (Oracle Cloud) objects | Pendo objects | How this pairing syncs | |
|---|---|---|---|
| Materialized views Precomputed result sets sometimes used as stable read sources for replication | 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 is specific to OCI Database (Oracle Cloud) and Accounts to Pendo — each maps to any object or custom field on the other side. | |
| Schemas Namespace boundaries that scope which objects a sync connection can access | 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 OCI Database (Oracle Cloud) and Feature Events to Pendo — each maps to any object or custom field on the other side. | |
| Sequences Key generators that matter when writing new rows from external systems | Page Events Page-view events for tagged pages; read-only via the Aggregation API, used for adoption and path analysis in a warehouse. | Sequences is specific to OCI Database (Oracle Cloud) and Page Events to Pendo — each maps to any object or custom field on the other side. | |
| PL/SQL procedures and packages Server-side logic that can react to synced data or transform it in place | Guide Events Guide seen/advanced/dismissed and step events for in-app walkthroughs; read-only through the Aggregation API to measure onboarding flow adoption. | PL/SQL procedures and packages is specific to OCI Database (Oracle Cloud) and Guide Events to Pendo — each maps to any object or custom field on the other side. | |
| JSON collections Document-style storage in the converged engine, synced alongside relational tables | Poll / NPS Responses Survey answers and NPS scores captured in-app (pollEvents / npsEvents); read-only via the Aggregation API as voice-of-customer data. | JSON collections is specific to OCI Database (Oracle Cloud) and Poll / NPS Responses to Pendo — each maps to any object or custom field on the other side. | |
| Partitions Physical table subdivisions relevant when replicating large fact 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. | Partitions is specific to OCI Database (Oracle Cloud) and Features / Pages / Guides (metadata) to Pendo — each maps to any object or custom field on the other side. |
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.
DetectionChanges in OCI Database (Oracle Cloud) are captured at the source via change data capture — no polling loop against its API. Log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling.
DeliveryEach detected change is written to Pendo through its API, with automatic retries and rate-limit backoff.
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 OCI Database (Oracle Cloud) as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every OCI Database (Oracle Cloud)–Pendo connection.
Changes in OCI Database (Oracle Cloud) or Pendo instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever OCI Database (Oracle Cloud) or Pendo data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single OCI Database (Oracle Cloud) or Pendo record.
Track your OCI Database (Oracle Cloud) ⇄ Pendo sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between OCI Database (Oracle Cloud) and Pendo.
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.
Authenticate OCI Database (Oracle Cloud) 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.
Pick the OCI Database (Oracle Cloud) 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between OCI Database (Oracle Cloud) and Pendo: authenticate both systems, choose the objects to sync (such as OCI Database (Oracle Cloud)'s Materialized views and Schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on OCI Database (Oracle Cloud): Log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling. On Pendo: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Pendo side: Features / Pages / Guides (metadata), Visitors, Accounts, Feature Events, plus custom fields where Pendo exposes them. On the OCI Database (Oracle Cloud) side: Tables, Views, Materialized views, Schemas. Stacksync auto-detects both schemas and converts types between the two systems.
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 OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud), where the services that read from the database act on them at query speed without calling the analytics API.
OCI Database (Oracle Cloud): SQL wire protocol (Oracle Net) via JDBC, ODBC, and native drivers; ORDS REST optionally exposes tables over HTTP. Authentication: Database credentials, commonly with mutual TLS using a client wallet on Autonomous Database; OCI IAM integration available. 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.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 406 integrations available for OCI Database (Oracle Cloud) and Pendo.