View Responses

Survey Responses Page

In this section, we explain how you can review the responses submitted by each participant using the Researcher Dashboard. We will also describe the metadata stored with each Survey response.

You can view participants' responses using the Survey Responses page on the Researcher Dashboard. On the top of the page, you can choose the Survey you want to view the responses for:

Note that you can't choose more than one Survey in the list because the columns for each Survey are different from the other ones. You only can download the responses for multiple Surveys at once. Doing so will create a ZIP file that contains multiple CSV files, one for each of the Surveys you have selected here.

In the Survey Responses table, each column represents a question in the Survey, the first column shows the Survey sessions, and on the next columns, each cell is for the response of the participant to that particular question in that particular session. You can click on the arrow button of each cell to see more information about it, if any.

If you click on any cell on the second row that points to an Answer, a dialog appears that shows the details of that Answer, such as the Answer given by the participant, the time that this Answer was given, or the location in which this response was provided (given that you have enabled the Capture Location option for your Survey):

Similarly, if you click on each cell of the first column, you can see the attributes for the relevant participant, such as the Device ID, Participant Status, Device Model, and other related data:

Data Filtering

After selecting the Survey you want to view responses for, clicking on the Filter button allows you to filter, sort, and organize your data as you want. Also, you can export your data as a CSV file when necessary. For more information on how to filter your data, see Data Filtering.

Survey Data Structure

When a Survey is prompted to a given participant, Avicenna opens a session that is associated with that Survey and to that participant. When the session is concluded, either because the participant completed the Survey, the Survey becomes expired after a certain time, or for any other reason, the Avicenna app collects all available responses and uploads the session together with its responses to the Avicenna servers. Each session has certain metadata which describes it. In turn, each response and question in a session also has certain metadata for itself. Below we describe this metadata in detail:

Session Metadata

The following describes the metadata stored with each session:

User ID:\ The Avicenna ID of the participant associated with this session is stored internally as user_id.

Activity ID:\ The ID of the Survey Activity for this session. Also indicates the expected questions and responses. Stored internally as activity_id.

Version:\ The Version of the Survey. If you modify your Survey while having active participants in the study, Avicenna uses versions to track who responded to which Version of your Survey. Internally stored as version.

Unique ID:\ A unique identifier for the session, stored internally as uuid.

Device ID:\ The ID of the device used by the participant to complete this session. Useful when a participant uses multiple devices for the study. Stored internally as device_id.

Scheduled Time:\ The time when the Survey was planned to be prompted to the participant. For Time-Triggered Surveys, this time is predetermined. For other Triggering Logics, such as proximity triggered, this time is recorded when the session is first created. Stored internally as scheduled_time.

Prompt Time:\ Refers to the specific time when the Survey is intended to be presented to the participants.

Record Time:\ The time when this session was concluded, either as completed, expired, blocked, or canceled (see here for the definition of each of these statuses), which is internally stored as record_time.

Status:\ The session Status, internally stored as status_id, with possible values:

• Completed: The Survey was completed by the participant.
• Canceled: The participant explicitly canceled responding to the Survey.
• Expired: The Survey was not responded to within the allocated time.
• Blocked: The Survey could not be triggered due to another active session for the same Survey for this participant.

Triggering Logics ID:\ The ID of the Survey's Triggering Logics that initiated this session is helpful when you anticipate your Survey being activated by various triggering methods. It enables you to identify which specific Triggering Logics was responsible for starting the current Survey session.

Triggering Logics Type:\ Refers to the type of Triggering Logics that is used for the current Activity. For more information on Triggering Logics Types check the Triggering Logics page.

Response Metadata

Each session contains a set of responses, one for each answer given by the participant. The metadata stored with each response is detailed below. Not all responses will have all of this information. For more about the response structure, the meaning of each field, and the expected hierarchy, consult the Survey Response schema.

Question ID:\ The ID of the question corresponding to the response, stored internally as q_id.

Question Type ID:\ The ID of the type of question that this response belongs to. It can be one of the following values:

• 0 - Single Answer
• 1 - Information
• 2 - Multiple Answer
• 3 - Text
• 4 - Number
• 5 - Image
• 6 - Audio
• 7 - Video
• 8 - Visual Analog Scale
• 9 - Mass
• 10 - Length
• 11 - Audio & Text
• 12 - Barcode
• 13 - Calendar

Internally stored as q_type_id.

Question Content:\ The content of the question that is posed to the participant. This may vary between sessions if the question features dynamic content, meaning the question content can change each time it is asked. Stored internally as q_content.

Answer ID:\ The ID of the answer chosen by the participant. This is only available for Single Answer and Multiple Answer questions. Stored internally as answer_id.

Answer Content:\ The content of the participant's answer. It can be a number (for number, mass, and length questions), a date (for calendar questions), or text (for text and barcode questions). Stored internally as answer_content.

Answer URL:\ The URL of the media submitted by the participant as their response to the question. Depending on the question type, the URL may point to an image, audio, or video file. Stored internally as answer_url.

Response Time:\ The time when the participant provided this response. It falls between the session's scheduled time and the record time. Stored internally as response_time.

Loop Count:\ The number of iterations the participant responded to this question. This applies when the question is part of a page located in a loop, meaning it is presented to the participant multiple times within the same session. Stored internally as loop_count.

Iteration:\ The latitude, longitude, speed, and accuracy values of the participant's GPS coordinates when answering the question. This data is only captured if the Survey is set to geo-tag responses and if the participant grants the Avicenna app the necessary permissions to access GPS. Stored internally as location.

Location:\ The latitude, longitude, speed, and accuracy value for the GPS coordinates of the participant while responding to this question. This is only captured if the Survey is set to geo-tag the responses. It also requires the participant to grant the Avicenna app the necessary permissions to access GPS. Internally stored as location.

Media Interactions:\ If the question content contains any videos, this attribute indicates how many times the video was watched and which parts were viewed. Stored internally as media_interactions.

Preferred Unit:\ The unit is chosen by the participant when responding to the question. For Mass questions, it can be Kg or Lbs, while for Length questions, it can be cm or ft & in. This field is not defined for other question types. Stored internally as preferred_unit.