In-App Survey Template for Product Growth

Microsurveys (1-2 questions) with contextual triggers typically achieve 15-30% response rates. Longer surveys (5+ questions) drop to 5-10%. The biggest driver of response rate is timing: surveys shown immediately after a relevant action outperform surveys shown on random page loads by 3-5x. Format also matters. A single thumbs-up/down question in a bottom bar gets higher response rates than a modal with a 10-point scale. Start with the simplest format that answers your [product-market fit](/glossary/product-market-fit) question.

Three rules. First, set a global cooldown of at least 30 days between any two surveys for the same user. Second, never run more than one survey per user segment simultaneously. Third, use sample rates so only a fraction of eligible users see each survey. Most teams over-survey their power users because those users trigger the most events. Protect your most active users from survey overload by capping impressions regardless of trigger frequency.

Modals get higher visibility but are more interruptive. Use modals for high-priority surveys (NPS, churn reasons) that you need every eligible user to see. Use inline prompts or slide-ins for feature feedback that should not break the user's flow. Bottom-bar prompts are a good compromise: visible but not blocking. Match the survey importance to the interruption level. The [PLG Handbook](/plg-guide) discusses how to balance in-product communication without degrading the experience.

Do not use in-app surveys when you need deep qualitative understanding (use interviews instead), when the topic is sensitive (users will not share salary or personal info in a popup), when you need responses from churned users (they are not in the app), or when you do not have a clear research question. Running a "general feedback" survey with no hypothesis is a waste of user attention and your analysis time. ---