Coming from Pendo
Import
The only analytics tool with first-class Feature entities: Pendo adoption data maps directly to UPG feature nodes.
The structural finding
Pendo is unique among analytics tools: it tracks named Features as first-class entities, not just events. A Pendo Feature maps directly to a UPG `feature` node with adoption_rate preserved as a property. This makes Pendo→UPG traceability uniquely complete in the analytics zone.
What UPG adds
Outcome connections: link Pendo feature adoption rates to the outcomes they were built to move.
Discovery evidence: adoption gaps surface as opportunities. ("Feature X has 3% adoption despite 80% awareness.")
Strategy context: NPS and feedback nodes linked to the features driving satisfaction scores.
Schema mapping
The key edge
The single most important semantic relationship this integration enables.
Defined in the UPG specification
Sample import
Pendo analytics: named Features with adoption + NPS + Feedback
Roundtrip
Import feature adoption and feedback data → link to outcomes and opportunities in UPG → push strategic context back to Pendo roadmap and feedback items via API.
- ·Outcome and hypothesis context added to Pendo feature metadata
- ·Research-backed user needs surfaced in Pendo roadmap item descriptions
- ·UPG opportunity links written back to Pendo feedback request items
How to import your Pendo data
The Pendo adapter is built and tested. A one-command import via the UPG CLI is in development:
This will fetch your Pendo data, map entity types automatically, and write everything to your graph. Today you can use the Markdown import or the adapter directly in code.
▸ For developers: use the adapter directly
Get started
The Pendo adapter ships in @unified-product-graph/adapters. Install it, then run the import command.
$ npm install -g unified-product-graph
# then import
$ upg import --from notion