Creating a DataSnap Report
DataSnap turns exactly one ODK audit-log CSV file or a connected form from an accessible, running SurveyLoopr-hosted ODK server into a structured data quality report. It uses the evidence present in that source to build report views for your team to review. Missing source data limits the available report views.
Start with the ODK submission review checklist when you need to confirm receipt, preserve the original export, and choose between a file-based review and a connected quality workflow.
What you'll need
- Access to a running SurveyLoopr-hosted ODK server and one of its available forms, or one ODK audit-log CSV file
- A SurveyLoopr account
How do I prepare DataSnap source data?
You can create a DataSnap report in either of two ways:
- Connect a form from an accessible, running SurveyLoopr-hosted ODK server through the available server, project, and form flow.
- Upload one audit-log CSV exported from ODK Central for one-time analysis.
If you still need a hosted ODK server, start with Getting a Server. If you need to prepare a form first, see How to Convert a Word or PDF Questionnaire Using LooprAI.
The uploaded CSV should be the form audit log file, usually named audit.csv, not a regular submissions CSV. Learn what the audit log records in the ODK form audit log documentation.
Step 1: Navigate to DataSnap
In your SurveyLoopr dashboard, click DataSnap in the left sidebar.
Step 2: Create a new report
Click New Report. A dialog appears asking you to:
- Give the report a name (e.g., "Baseline Survey — Round 1 QC")
- Connect a form from your SurveyLoopr server, or choose CSV upload
- Upload your ODK form audit log CSV if you are using the CSV path
Click Create Report. DataSnap creates a report from the available audit-log evidence for your team to review.
DataSnap's upload path accepts one ODK audit-log CSV. When an eligible hosted connection is available, you can use the server, project, and form flow instead.
Step 3: Explore the report
A DataSnap report presents the following current sections when the source contains the required evidence:
Summary cards
At the top, you'll see key metrics:
- Total interviews
- Average interview duration
- Median interview duration
- Flagged interviews
- Active days
Activity and time views
DataSnap shows Surveys per day, a Daily time-use heatmap, and Time by group or variable when the source contains usable timing evidence. These views summarize recorded interview activity and working time. They do not provide automatic per-enumerator rankings.
Question and interview review
Use Question friction, Flagged interviews, and Interview details to identify records and questionnaire paths that deserve contextual review. A flag is a prompt to investigate, not a verdict about an interviewer or submission.
Survey concentration map
A 3D survey concentration map can show recorded interview locations when the source contains usable GPS evidence. Reports without usable GPS data do not show this view. Use the map alongside the report's interview details; DataSnap does not score locations against an expected survey area.
The audit log section is only available if you enabled ODK audit logging in your XLSForm before data collection. You cannot add audit logging retroactively to existing submissions. See the How to Analyze Audit Log Data guide for setup instructions.
Step 4: Share the report
DataSnap reports can be shared through a configured view-only link.
- Click the Share button in the report header
- Enable Public Link
- Copy the link and share it
The configured view-only link does not grant a SurveyLoopr account or editing access. Its availability and expiry follow the settings selected by the report owner.
Step 5: Connect a hosted server (optional)
Instead of uploading an audit-log CSV manually, you can create a connected report from an accessible, running SurveyLoopr-hosted ODK server. From the report creation dialog, select the available server, project, and form flow. DataSnap does not promise a fixed update interval; review report status in the application.
DataSnap highlights patterns worth investigating. It does not prove fraud, misconduct, or data quality by itself; review the form, field protocol, geography, and study context with the team.
Learn more about creating the server side of this workflow in Getting a Server.
What's next?
Explore the Tips & Tricks section to get more from your ODK forms and DataSnap reports.
Read: How to Analyze Audit Log Data →Frequently Asked Questions
What data sources does DataSnap support?
DataSnap supports two source paths: exactly one ODK audit-log CSV file for manual upload, or a connected report from an accessible, running SurveyLoopr-hosted ODK server through the available server, project, and form flow.
What does DataSnap analyze from audit logs?
DataSnap shows overview metrics, surveys per day, daily time use, time by a group or variable, question friction, flagged interviews, interview details, and a survey concentration map when usable GPS exists. Review these patterns with the field protocol and study context; they do not prove fraud or misconduct.
Can I share DataSnap reports with stakeholders?
Yes. A report owner can create a configured view-only link. Recipients can view that shared report without receiving a SurveyLoopr account or editing access. Link availability and expiry follow the owner's selected sharing settings.
How often do connected server forms sync?
DataSnap does not promise a fixed update interval. Connected reports use the available SurveyLoopr-hosted server workflow, and update behavior can depend on server access, source data, and processing. Review the report status in the application.
Do I need ODK audit logging enabled for DataSnap?
Audit-event analysis requires ODK audit logging to be enabled in the XLSForm before data collection begins. It cannot be added retroactively to completed submissions. Missing source data limits the available report views, including GPS, timing, and detailed interviewer-behavior evidence.
No Credit Card Required
Build the form first. Add hosting when you need it.
Start free with LooprAI, then deploy a managed ODK Central server or run DataSnap checks when your project is ready.
Automation handles the mechanical work.
Researchers decide what the evidence means.