Survey Results Export Format

When a participant completes a survey, it generates a Survey Result. Each survey result contains multiple step results (corresponding to each step of the survey), and each step result can contain multiple child results (answers to questions, results produced by active tasks, etc.). In some cases (e.g., instruction steps, or if a step was skipped)—a step result may not have any child results.

Survey Result Component Data

In the CSV export, multiple data files are produced for survey results for the different survey result components, with keys that can be used for cross referencing. In the JSON export, all of the results are contained in a single file and data structure. Deleted survey results will always be contained in a distinct file in both CSV and JSON format.

For more information about how to cross-reference data across the different survey result components, see Export File Type and Format Summary. For more information about the other components, see the following topics:

Data Fields

Field	Description
`SurveyResultKey`	A unique, auto-generated key for this result. Can be used to cross reference with other survey results.
`SurveyKey`	A unique, auto-generated key for the survey which will not change if the survey name changes.
`SurveyName`	The name of the survey this result was for.
`SurveyVersion`	Identifies which version of the survey was active at the time the data was collected. This allows you to adapt data processing if your survey changes.
`ParticipantIdentifier`	The identifier of the participant this task was for. Can be used to cross reference with Participants.
`ParticipantID`	The stable, automatically generated, internal system identifier for this participant. Universally unique identifier (UUID).
`SurveyTaskKey`	The key for the task used to deliver this survey. Can be used to cross reference with Survey Tasks. Will be empty for “Consent” survey results - results captured during the consent process do not have a survey task.
`Type`	One of “Survey” or “Consent.”
`StartDate`	The timestamp for when the participant began taking the survey, in ISO 8601 format. Includes timezone offset information.
`EndDate`	The timestamp for when the participant finished taking the survey, in ISO 8601 format. Includes timezone offset information.
`DevicePlatform`	The platform the survey was completed on, e.g., “iOS,” “Android.”
`DeviceName`	The name of the device used to complete the survey, e.g., “iPhone 8,2.”
`DeviceOSVersion`	The operating system version running on the device used to complete the version, e.g., “11.2.5.”
`InsertedDate`	The creation date of the result, in ISO 8601 format. Is always in UTC.
`ScheduleID`	The ID assigned to the schedule in MyDataHelps Designer.
`ScheduleInterval`	The timepoint relative to the the start date of the schedule for this result, expressed in units defined by ScheduleIntervalType. For example, if a schedule delivers tasks every 2 weeks, then this field would have ScheduleInterval values `2`, `4`, `6`, etc.. This field is only populated for survey results that are from repeated event- or date-based schedules.
`ScheduleIntervalType`	Used in conjunction with ScheduleInterval to determine the timepoint relative to the the start date of the schedule for this result. Value can be `Days`, `Weeks`, `Months`, or `Years`. This field is only populated for survey results that are from repeated event- or date-based schedules.
`ScheduleName`	Name given to the schedule in MyDataHelps Designer.
`ScheduleCategory`	The user-defined category for the schedule. See Schedules Types for more information on categories.
`UserType`	The type of user that submitted the survey, for example Participant or Coordinator.
`User`	The user that submitted the survey. For a survey submitted by a Coordinator, this will be the coordinator’s email address. For a survey submitted by the Participant, this will be empty.
`Locale`	Which language the survey was taken in, for example "es" or "nl". If taken in the Default language, this field will be empty.
`Event`	The event associated with the survey result. Events are an optional feature, and this field is only populated if events are configured for the project and there is an event assigned to the result. See Tracking Survey Completion with Events for more information.

Sample CSV Export

SurveyResultKey,SurveyKey,SurveyName,SurveyVersion,ParticipantIdentifier,SurveyTaskKey,Type,StartDate,EndDate,DevicePlatform,DeviceName,DeviceOSVersion,InsertedDate,ParticipantID,ScheduleID,ScheduleInterval,ScheduleIntervalType,ScheduleName,ScheduleCategory,UserType,User,Locale,Event
a843228f-6369-f011-ad1f-0e0e6a19462f,3c1faa38-b8c4-eb11-aaab-0afb9334277d,Daily Mood Survey,0,MDH-808,50069b40-5769-f011-ad1f-0e0e6a19462f,Survey,2025-07-25T10:27:42-04:00,2025-07-25T10:28:02-04:00,WebClient,,,2025-07-25T14:28:02Z,ba5ba41b-a375-42fb-83d3-9c6d12554229,df5673b4-247e-4212-ae86-d363aed57693,0,Days,Day after Survey,Post-Surgery,Participant,,,

Sample JSON Export

{
 "SurveyResultKey": "a843228f-6369-f011-ad1f-0e0e6a19462f",
 "SurveyKey": "3c1faa38-b8c4-eb11-aaab-0afb9334277d",
 "SurveyName": "Daily Mood Survey",
 "ParticipantIdentifier": "MDH-808",
 "ParticipantID": "ba5ba41b-a375-42fb-83d3-9c6d12554229",
 "SurveyTaskKey": "50069b40-5769-f011-ad1f-0e0e6a19462f",
 "Type": "Survey",
 "SurveyVersion": 0,
 "StartDate": "2025-07-25T10:27:42-04:00",
 "EndDate": "2025-07-25T10:28:02-04:00",
 "DevicePlatform": "WebClient",
 "InsertedDate": "2025-07-25T14:28:02Z",
 "UserType": "Participant",
 "StepResults":[
  {
  "SurveyStepResultKey": "b343228f-6369-f011-ad1f-0e0e6a19462f",
  "StepIdentifier": "Guilty",
  "StartDate": "2025-07-25T10:27:43-04:00",
  "EndDate": "2025-07-25T10:27:46-04:00",
  "Results": [
  {
   "Type": "QuestionResult",
   "QuestionResultKey": "cd43228f-6369-f011-ad1f-0e0e6a19462f",
   "ResultIdentifier": "Guilty",
   "Answers":[
    "1"
   ],
   "StartDate": "2025-07-25T10:27:43-04:00",
   "EndDate": "2025-07-25T10:27:46-04:00"
  }]
 }],
 "Schedule": {
  "ID": "df5673b4-247e-4212-ae86-d363aed57693",
  "Interval": "0",
  "IntervalType": "Days",
  "Name": "Day after Survey"
 }
}