Survey Diagnostics Funnel
Understand the estimated population of end users at particular steps in Sprig’s survey selection and contact engine
Survey Diagnostics Funnel Overview
The Survey Diagnostics Funnel allows you to understand the estimated population of end users at particular steps in Sprig’s survey selection and contact engine. The funnel will enable study owners to self diagnose why they may not be getting as many responses as expected and troubleshoot survey design.
Using the Diagnostics Funnel
- For any active or completed Web or Mobile Survey, navigate to the Survey Results page.
- Select Inspect to launch the Inspect Response Rate modal.
- The debugger will show you a list of checkpoints and the estimated population of end users at each checkpoint.
Note on Limitations:
- Survey Diagnostics Funnel will be unavailable for surveys completed before October 2023.
- Audience population estimations are limited to the last 30 days of an active survey.
- If any edit is made to an active study, including copy updates or targeting criteria, the diagnostics funnel will reset and begin collecting data from time last updated.
Checkpoints
Checkpoint steps and corrective measures are detailed below:
Checkpoint | Step Details | Possible Corrective Measure |
---|---|---|
Has required SDK* | Users that are sent to Sprig and have the correct SDK installed | Update SDK version |
Met resurvey criteria | Users that are qualified based on global or survey level recontact period settings | Override global contact period, or adjust survey level recontact period |
Triggered event | Users that triggered the survey contact event | Add additional events to trigger this survey |
Hadn't seen this study yet | Users that have not seen this survey before (Shown only when “Show once per user” is on) | Adjust “Show once per user” setting |
Matched filters | Users that meet Audience, Event, or Group targeting filter criteria (Shown only when at least one filter set) | Adjust filter settings to be more inclusive, or verify that filters are configured correctly |
Included in send limit | Study send limit (#of times per day or sampling) settings are captured under Audience > Response settings (Shown only when this count is different than the previous stage) | Adjust sampling or send limit criteria to be more expansive |
Selected for this study | Step is relevant only when multiple studies have the same targeting criteria (Shown only when # selected for this study differs from previous step) | Modify this study, or a conflicting study to have different triggering events |
Received study | Users that have received the study | N/A |
Viewed study | Users that have viewed the study | Modify the "waiting period" delay to be shorter |
Started responding | Users that have started responding | N/A |
Completed study | Users that have completed the entire survey | Update study design (shorter, question types, etc) to increase completion rates |
*For mobile studies, if SDK update is bundled with an app update, end users will need to update your native app in order to qualify for a study with a minimum SDK requirement.
FAQs
How is overall response rate calculated?
The response rate graph is calculated by dividing the number of responded surveys by the number of seen surveys within a day based in Universal Time Coordinated (UTC).
Updated 12 months ago