Connect your platform.
Give Questra access to the test survey and its response records.
CONFIDENCE IN YOUR DATA
Trust what lands
in your dataset.
Match simulated sessions to response records in your survey platform. Check the codes, values, and hidden questions against your questionnaire—before fieldwork begins.
Test your survey dataRequires a supported platform connection with access to test response data.SIMULATED SESSION#002
- Coffee frequency
- Sometimes
- Brand selected
- Harbor
MATCHED TO ITS RESPONSE RECORD
YOUR PLATFORM’S DATA#002
| Field | Expected | Recorded | Result |
|---|---|---|---|
| Q1Frequency | 2 | 2 | |
| Q2Brand | 20 | 20 | |
| H_USAGEHidden group | 2 | 1 |
Right answers. Wrong hidden group.
An occasional coffee drinker was recorded in the daily group. H_USAGE should be 2, not 1.
CONNECT THE EXPERIENCE TO THE EVIDENCE
Every test session.
Its own data trail.
A survey can look right and still record the wrong thing. Connecting to your platform lets us follow the answer all the way through.
Put it through its paces.
Simulated respondents try answers and follow different paths through the survey.
Match the records.
Link each captured response record to its simulated session. Compare what was answered with what was stored.
Your questionnaire is the reference.
The coding and assignment rules you specify become the expectations we check.
VISIBLE ANSWERS. INVISIBLE ASSIGNMENTS.
Check every code.
Even the questions they never see.
From a selected brand to a derived segment, test whether the recorded data follows your research design.
Harbor20
Answer codes.
Single and multiple selections, “other” answers, and opt-outs. Verify that the right choices become the right codes.
3 cups a day3
Values & recodes.
Numbers, open text, other-specify responses, and derived values. Check what lands against what was expected.
SometimesH_USAGE = 2
Hidden questions.
Usage groups, segment assignments, and hidden variables. Verify the rules that shape your analysis behind the scenes.
LESS SURPRISE AFTER FIELDWORK
Fieldwork finishes.
Analysis can begin.
Find miscodes and incorrect assignments while there’s still time to fix the survey. Go into fieldwork with greater confidence that your dataset will be ready when your analysts are.
See how findings are reportedBEFORE YOU FIELDGive the data
Give the data
a dress rehearsal.
Compare against the questionnaire
Trace mismatches to their source
Fix the survey and test again
A few practical questions.
Can Questra verify survey codes and hidden variables?
Checks can cover selected-answer codes, recorded numeric or text values, recodes, other-specify text, and hidden-variable assignments described in the questionnaire. Questra compares those expectations with captured test response records.
How are simulated sessions matched to respondent data?
With a supported survey platform connection, Questra captures response records for simulated sessions and attaches them to the evidence from those sessions. That connects the answers and paths observed in the browser with the values the platform actually stored.
Can data checks run from a survey URL alone?
A URL is enough for browser checks, but recorded-data checks require a supported platform connection and access to response records on a test copy. Without that access, the report marks affected checks as unavailable rather than claiming they passed.
What does a data finding show?
A finding connects a coding or hidden-question rule from your questionnaire with the simulated session and its recorded data. Use that evidence to locate miscodes, incorrect recodes, or hidden assignments, then update the survey and rerun checks before fieldwork.