debugging-surveys

Diagnose PostHog Surveys display, eligibility, and response issues across web and mobile SDKs.

713|118|Updated Aug 11, 2020
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill debugging-surveys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-surveys
Source: https://github.com/PostHog/posthog-foss/tree/main/products/surveys/skills/debugging-surveys
Command: npx skills add https://github.com/PostHog/posthog-foss --skill debugging-surveys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Support tickets about PostHog Surveys — surveys not showing, fewer responses than expected, incomplete-looking responses, or accidental submissions — are usually eligibility or configuration issues rather than SDK bugs, and misdiagnosing them leads to costly wrong advice like rebuilding surveys.

Core Features & Use Cases

  • Eligibility pipeline tracing: Walk the web SDK's ordered eligibility checks (running state, linked/targeting flags, wait period, seen flag) to find exactly which gate failed and why.
  • Cross-SDK parity table: Verify whether a feature (URL targeting, popup delay, partial responses, auto-submit) is even supported on the customer's platform before investigating it.
  • Response data interpretation: Decode partial responses, branching-skipped questions, and optional questions so complete-but-sparse responses are not misread as broken submissions.
  • Diagnostic HogQL queries: Run read-only query templates (shown vs sent ratios, flag evaluation, latency analysis) via the PostHog MCP against the customer's project.
  • Use Case: A customer reports "only the first question was answered." The skill guides you to check per-question branching and optional fields in the survey JSON, revealing the blank cells are questions respondents were never shown — an expected complete response, not a bug.

Quick Start

Paste a PostHog Surveys support ticket and ask the AI to diagnose why the survey is not showing or why responses look incomplete.

Frequently Asked Questions about debugging-surveys

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why is my PostHog survey not showing to users?

Most survey-not-showing cases are eligibility failures, not rendering bugs. The SDK checks running state, linked and targeting flags, wait period, and per-survey seen status in order, and the first failure silently blocks display. Check which gate failed using feature flag events and the survey JSON.

How do I debug fewer survey responses than expected in PostHog?

Compare survey shown versus survey sent event counts before and after the suspected change. If the sent-to-shown ratio is stable, the problem is upstream eligibility such as a wait period or cohort change, not rendering or submission.

Does PostHog Surveys support partial responses on mobile SDKs?

No, partial responses and auto-submit are web-only features in posthog-js. iOS, Android, Flutter, and React Native always store one response at the end of the survey, so web diagnoses should not be carried onto mobile tickets.

Why do PostHog survey responses look incomplete with only the first question answered?

Blank cells usually mean questions were skipped by branching or marked optional and clicked past, which still counts as a complete response. Check each question's branching and optional fields in the survey JSON before treating it as a bug.

Why does a PostHog survey submit without clicking a submit button?

The skipSubmitButton setting, labeled Automatically submit on selection, records the answer and advances in one click with no confirmation. It is on by default in survey templates and is web-only, so sub-10-second completions on multi-question surveys are its signature.

Can Android apps render PostHog surveys natively?

No, the Android SDK ships no built-in survey UI and only handles eligibility. The app must provide a PostHogSurveysDelegate to render surveys, so a survey never rendering on Android is often a missing delegate rather than a PostHog bug.