Build a useful feedback loop

Choose your first feedback moment

Start where a user has something specific to tell you. Each recipe includes the question, follow-up logic and a way to interpret the answers.

• Understand what interrupts onboarding →

  Ask why someone paused setup, then follow up when more detail would help.

• Learn why customers cancel →

  Collect optional feedback after cancellation is confirmed, with a copyable survey recipe.

Add feedback to your stack

Run a tested example, connect your own site and verify that your first response is saved.

• Next.js integration guide →

  Connect UserReason to an App Router project and trigger an onboarding survey from an explicit action.

• React integration guide →

  Use the Vite example to add optional feedback after a successful product action.

Choose how to run your surveys

Compare the work you would own, the workflow you want and the response volume you expect.

• Build your own surveys or use UserReason? →

  See what a homegrown survey system adds to your roadmap, and try a working comparison.

• UserReason vs PostHog Surveys →

  Compare the developer workflow, free response allowances and reasons to choose UserReason.

Inspect the engineering

• How we test in-app surveys before shipping →

  Run the public-SDK example and inspect its 15 answer-route checks and verification record.

• Engineering notes →

  Walkthroughs built around working code and repeatable tests.

Set up your development workflow

• Work with your coding agent →

  Use the CLI or MCP to prepare survey drafts and review responses with supporting evidence.

• SDK and product documentation →

  Find the current API reference, targeting rules, identity options and management commands.

• Start with 10,000 free monthly responses →

  See the per-workspace allowance, how responses count and Enterprise options.