Check fieldwork and get your data out

Completed responses and partial attempts

Partials are especially useful for understanding drop-off. If someone later resumes and submits, Dayalogs treats that attempt as completed instead.

A demographic screen-out is stored as a completed terminal response with the screened_end outcome. It remains visible and available, but exports exclude it by default so you do not pay for it accidentally. Select Include screened-out responses when its answers are useful.

Inspect and compare responses

Use the Responses tab to search, sort, filter by confidence and place up to five answers side by side. Open a response to see its answers, collection date, survey version, source link and the useful context attached to it.

• Compare selected questions without exporting the whole dataset.
• Review contact, link and survey variables when they help explain an answer.
• Open the confidence explanation when a response needs attention.
• Download one response and any uploaded files as a ZIP.

Completed responses also keep an approximate two-letter country code and a coarse device category: desktop, mobile, tablet or unknown. Country resolution runs asynchronously, so a new response may show an unknown country briefly or permanently when lookup is unavailable. Dayalogs does not retain the raw IP or full user agent as response metadata.

IP address country data powered by IPinfo.

For what the confidence score means and what it does not prove, see Response confidence.

Compare survey versions safely

Each attempt keeps the questionnaire version on which it started. Publishing an update never changes the questions under someone who is already answering.

When you analyze or export data, choose the current version, one historical version or all versions. If the questionnaire changed substantially, compare versions separately before combining their results.

Search, confidence filters and sorting run across the complete selected scope. On desktop you can page through every matching response; compact screens load those same result pages progressively.

Choose the right export

Team+ SPSS .sav export is available on Team and Enterprise. CSV, XLSX, JSON and NDJSON are available on every plan.

Choose whether to export completed responses, partial attempts or both. For partials, you can require that the attempt reached or passed a particular question, even when survey logic skipped that exact question and continued later. Screened-out terminal responses remain excluded unless you opt in.

Collection itself does not spend wallet balance. The final wizard step states This export will cost €X from your wallet and shows the exact candidates, already billed attempts, newly billable attempts and projected balance before confirmation. MCP assistants must report the same exact preview cost and obtain your approval before exporting. Every included attempt is charged only on its first real export; a partial that later completes is not charged again. If the candidate population or options change before download, Dayalogs requires a fresh approval. Insufficient balance blocks that export atomically, but never pauses live surveys.

JSON and NDJSON preserve the complete saved @urlparams snapshot. CSV, XLSX and SAV add stable urlvar_* columns for respondent URL parameters while omitting Dayalogs transport controls.

Keep uploaded files connected and private

Uploaded files are stored privately and remain linked to the response and question that produced them. A raw storage URL does not grant public access.

A ZIP export includes the selected response data, the files and a manifest that maps every file back to its response and question. A single-response download contains a readable CSV and that response's files; it previews the wallet impact and uses the same once-per-attempt billing as the export wizard.

Delete only when you mean to

Deleting a response is permanent. For normal analysis, use filters or exports instead. Reserve deletion for test submissions or a clear privacy and retention request.