Pendo → Azure Synapse
AI-first ETL from Pendo into Azure Synapse. Governed entities, incremental sync, typed landing tables.
How Datrise loads Pendo into Azure Synapse
Datrise syncs Pendo's events, guides, NPS, feature adoption, and account metadata into Azure Synapse as a typed table per source entity. Flexible or custom fields land in NVARCHAR(MAX) JSON columns, and timestamps such as created, updated, and status changes are typed as datetime2.
Sync is incremental: Datrise uses COPY into staging, then a MERGE on stable id, so re-runs update only what changed. Hash distribution on the join id with date partitioning on facts. Synapse dedicated pools reward good hash-distribution choices, so Datrise distributes on entity ids to avoid data-movement-heavy joins.
Ideal for Azure analytics estates feeding Power BI.
Endpoints
Pendo: Product analytics and in-app guidance for SaaS teams.
Azure Synapse: Microsoft analytics workspace with SQL pools.
How Pendo entities map to Azure Synapse
| Pendo entity | Azure Synapse object | Notes |
|---|---|---|
| events | pendo_events | datetime2 events |
| guides | pendo_guides | id PK · linked to pendo_events |
| NPS | pendo_nps | id PK · linked to pendo_events |
| feature adoption | pendo_feature_adoption | id PK · linked to pendo_events |
FAQ
How does Datrise handle Pendo's custom fields in Azure Synapse?
Flexible values are stored as NVARCHAR(MAX) JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Azure Synapse types.
How does the Pendo to Azure Synapse sync stay up to date?
It runs incrementally — Datrise uses COPY into staging, then a MERGE on stable id.
Related pipelines
More destinations for Pendo
More sources for Azure Synapse
Early access
Connect Pendo to Azure Synapse the easy way
Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.