NPS & Listen surveys
Surveys live in a separate Pendo Listen SKU, with capped question types and no branching unless you upgrade tier.
What people actually say
✕Pendo Listen is sold as a separate add-on that can add roughly 30% on top of license costs, on top of an already six-figure base for mid-market customers.
Source: Costbench, Pendo pricing breakdown ↗✕Survey capability is restricted — reviewers call out the lack of certain question types and limits on follow-up questions after NPS responses, which prevents nuanced feedback collection.
Source: UserGuiding, Pendo reviews 2026 ↗✕Surveys and NPS live in different modules from analytics, leading to data discrepancies and forcing teams to reconcile feedback against product usage by hand.
Source: Userpilot, Pendo analytics review ↗
NPS is a Postgres table plus a Next.js modal triggered by your event store. Branching logic is a switch statement; follow-ups are extra rows. Responses join straight onto the user's event history — no Listen SKU, no module reconciliation, and the data exits to Slack or HubSpot via a webhook you wrote.