Surveys

Contents

Surveys collect qualitative feedback from your users – NPS, product-market fit, churn reasons, or plain open text – and put it next to everything else PostHog already knows about them. Ask the right people at the right moment with targeting built on the same events, properties, cohorts, and feature flags you use everywhere else.

Because responses land as events, every answer carries the respondent's session replay, events, and person properties, so "the checkout is confusing" comes with the recording that proves it.

Get started

Where you can use it

You build surveys and read responses in the PostHog web app. The other surfaces let you create, launch, and analyze surveys from your editor or your own scripts.

PostHog Web

Build, target, and launch surveys, then read the results with replays attached.

Build a survey →

PostHog MCP

Create, launch, stop, and summarize surveys from any MCP client or AI editor.

Manage surveys →

API

Manage surveys and pull responses programmatically from your own tooling.

Use the API →

Where its data comes from

Surveys run on the questions you ask, who you ask them of, and the responses that come back. SDKs render and display surveys in your product, targeting decides who sees what, and every answer is captured as an event you can query like any other.

SDKs

Show surveys in web, mobile, and framework apps with the SDK you already installed.

Install an SDK →

Questions and targeting

Branch questions on earlier answers and pick who sees a survey with URLs, events, properties, and flags.

Design questions →

Responses

Every answer is an event, so you can chart it, query it in SQL, or pipe it to Slack and webhooks.

View results →

Still have questions?

Was this page useful?