Target PostHog Surveys to Relevant Users
Show the survey when an eligible user has enough context to answer, then test both inclusion and exclusion. The targeting rule should reflect the research question rather than merely maximize response volume.
Before you start: Have a survey draft, supported SDK and an eligibility definition. Check available URL, event and property targeting for the current implementation.
Worked example: Ask about export usefulness after a successful export, not immediately after signup. Keep users who cannot access export outside the audience.
Step-by-step guide
Define the research audience
Write which users can answer meaningfully and which cannot. Include plan, role and recent product experience where relevant.
Choose a useful moment
Select a trigger that follows the experience being evaluated. Avoid interrupting an unfinished high-stakes action merely because the page is easy to target.
Configure supported conditions
Use documented URL, event or property rules. Verify whether a proposed cohort or flag condition is supported before promising behavioral targeting.
Test boundary cases
Use a qualifying user, a non-qualifying user and a person who already responded. Confirm timing and repeat behavior match the intended experience.
Review interruption cost
Check small screens, keyboard behavior and interaction with other surveys. Reduce frequency or move the prompt when it blocks the task.
Launch with a monitoring plan
Record the audience and rule version. Watch display, dismissal and response behavior, then interpret answers as feedback from that selected audience.
Common mistakes
Ask before experience
A new user cannot evaluate a feature they have not used.
Broad URL match
A route pattern can include unrelated pages. Test real URLs and navigation.
Responses treated as representative
Targeting and voluntary participation select the sample. State who was asked.
Tips
Write an exclusion case before launching.
Keep the prompt away from a critical submission moment.
Save the targeting version with the response readout.
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.