Product workflows2026-10-272 min read

Analyze PostHog Survey Responses by Segment

Interpret responses alongside who saw the survey, who dismissed it and who answered. Segment differences can suggest follow-up questions; they do not automatically establish prevalence across all customers.

Before you start: Have the survey’s targeting definition, response data and appropriate person properties. Avoid exporting unnecessary identifying details for synthesis.

Worked example: An export survey receives complaints from first-time users and praise from repeat users. Compare exposure and response context before declaring the feature successful or broken overall.

Step-by-step guide

01

Reconstruct the audience

Record targeting, dates and the product moment that triggered the survey. Note whether eligibility changed during collection.

02

Inspect exposure and response

Review seen, dismissed and submitted counts where available. A high score from a small selected subset needs different interpretation from broad participation.

03

Choose meaningful segments

Use a small number of relevant groups such as first-time versus repeat users. Check group sizes before comparing averages or percentages.

04

Code open-text evidence

Group observations by underlying problem while keeping source context. Preserve disagreement and distinguish multiple comments from one person from distinct respondents.

05

Connect to behavior

Compare a proposed issue with relevant product events or research. Treat a request as a clue to a problem rather than automatically as a feature requirement.

06

Write the decision note

Summarize findings, sample limitations and next steps. Keep evidence links available to authorized readers and avoid implying the survey represents everyone.

Common mistakes

No exposure denominator

Response counts alone cannot show participation. Review who was actually asked.

Tiny segments ranked

Small groups can produce unstable apparent differences. Report counts and uncertainty.

Requests become requirements

Understand the problem and context before adopting the requested solution.

Tips

Keep contradictory comments in the synthesis.

Separate respondent counts from comment counts.

Record targeting changes beside the response period.

Sources and verification

Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.

Frequently asked questions

Spend less time on setup, more on decisions

Vantage connects your tools and generates specs grounded in real data. Free to start.

Try it free, no sign-up

Before you set this up, check what customers are actually asking for.

Paste call notes, support tickets or feedback. Vantage pulls out the signals and themes in about 30 seconds.

Free to start. No credit card required.

Related reading