Help Center
Responses & Data Collection
Monitor live responses, collection quality, respondent channels, and data hygiene.
What this guide helps you do
Monitor live collection, verify data quality, remove test noise, and prepare responses for reliable analysis.
Before you start
- Publish the survey or have existing responses.
- Know which channels are collecting data.
- Decide which test responses should be excluded.
What you will do
- Open response view
- Check collection status
- Filter by source and channel
- Clean before analysis
You are done when
- Collection status is healthy.
- Test or incomplete data is identified.
- Filters and segments are ready for analysis.
Overview
Response collection is where published surveys become usable evidence. Track completion, source, timestamps, metadata, consent, and answer quality as data arrives.
When to use this feature
Step-by-step guide
Open response view
Choose the survey and inspect the responses table or response detail view.
Check collection status
Confirm the survey is open, response limits are not reached, quotas are healthy, WhatsApp/email batches succeeded, and sources remain active.
Filter by source and channel
Compare labelled short URLs, embed traffic, WhatsApp completions, invitations, reminders, geography tags, completion states, consent flags, duplicate signals, partial vs complete.
Clean before analysis
Flag test submissions, panel dupes, or partial fraud before syncing to dashboards or downstream BI.
Quality signal
The first 20 responses often reveal whether your question wording is clear enough to scale.
Screens / UI explanation
Response tables audit individual answers; collection dashboards summarize velocity.
Source dimensions map directly back to labelled distribution links.
Best practices
Remove pilot responses before stakeholder readouts.
Document any retargeting or reminder waves applied mid-field.
Treat partial responses as signals for dropout analysis in Advanced Analytics.
Tips
Compare response channels to learn where your audience actually engages.
Use filters before exporting only the data stakeholders need.
Common issues
Responses stopped arriving.
Check publish state, plan limits, expiry date, and whether the distribution link changed.
Data includes internal tests.
Filter by timestamp, email, or marker answers and exclude test entries from reports.