Docs

PostHog Mobile Survey Intro Screen Tracking

PostHog mobile survey intro screens now work on iOS, Android and Flutter. Track survey intro drop-off and response rate before you lose feedback.

Engagement

On 4 September 2026, PostHog added an optional introductory screen to mobile surveys on iOS, Android and Flutter. Instead of dropping the first question straight onto the screen, a survey can now open with a short message explaining why you are asking, how long it will take and what you will do with the answers.

This matters because in-app surveys are interruptions. A user in the middle of a task sees a question card and has about a second to decide whether to engage or swipe it away. Before an intro screen existed, a low response rate gave you one number and no explanation. Was the question wrong, the timing wrong or the survey simply unwelcome? With an intro screen, you add a new step to the funnel, and a new place for people to leave, which you need to measure to know whether it helps.

Without tracking it, you can easily make things worse. A long introduction might cut completions, while a clear one might lift them. You will only find out by comparing versions.

Data Points to Track

  • survey_shown: with survey_id, platform (iOS, Android, Flutter), app_version and the screen or trigger that displayed it
  • has_intro_screen: true or false, so surveys with and without the introduction can be compared
  • intro_to_first_question_rate: the share of users who move past the intro to the first question
  • intro_dismissed: users who close the survey on the intro screen, with time spent on it
  • survey_completed and survey_abandoned, including the question number where people stopped
  • intro_word_count and stated_duration, if your intro promises a length such as “2 minutes”
  • User context: session count, days since install and plan, to avoid surveying people at the wrong moment

Setup Steps

  1. Update the PostHog mobile SDK to a version that supports survey introductions on your platform, and check the PostHog changelog for the version.
  2. Pick one survey to test. Use a short, existing survey such as a post-onboarding or feature feedback question so you have a baseline.
  3. Create two variants. One has no intro and the other has a short intro screen with a clear purpose and an honest time estimate.
  4. Split users randomly using a feature flag, and record the variant on every survey event.
  5. Capture the extra funnel step. Make sure shown, intro passed, first question answered and completed are all recorded as separate events.
  6. Compare after a fixed number of responses. Wait for enough survey impressions in each group before deciding, and compare by platform as well as overall.

Actionable Insights

If the intro passes most users but completion barely moves, the screen is harmless and you can keep it for context. If the intro causes a large drop-off, it is probably too long or arrives at a bad time. Shorten it, or move the survey to a calmer moment such as after a task is finished.

Look at the platform split. A rate that is fine on iOS but poor on Android could point to a layout problem, such as text being cut off on smaller screens, rather than a copy problem.

Check who responds, too. If completion rises but only among your most engaged users, you may be getting more answers while learning less. Compare the segments that responded with the ones who were shown the survey.

Finally, track the time between intro and first answer. A long delay suggests the introduction makes people read more than they want to. A short one with a high pass rate suggests the survey is easy to start.

Expert help

Need help tracking this in your app?

Our team sets up analytics pipelines for mobile and web teams every day. Talk to us and get your first events flowing in under an hour.

Talk to an expert