{"id":9018,"date":"2021-09-03T09:43:33","date_gmt":"2021-09-03T09:43:33","guid":{"rendered":"https:\/\/m-path.io\/manual\/?post_type=ht_kb&p=9018"},"modified":"2026-05-11T11:59:43","modified_gmt":"2026-05-11T11:59:43","slug":"export-data","status":"publish","type":"ht_kb","link":"https:\/\/app-manual-wp-001-atfsdabuggg7fzdq.germanywestcentral-01.azurewebsites.net\/knowledge-base\/export-data\/","title":{"rendered":"Export data"},"content":{"rendered":"\n

There are two ways of exporting data from your dashboard: single participant export in the Visualize tab, or advanced export of a larger dataset for statistical analysis in the Export tab (available for premium subscriptions only).<\/p>\n\n\n\n

Export plain data of a single participant <\/h3>\n\n\n\n

You can export a very simple representation of the data of an individual participant in the Visualize tab. You do this by selecting table <\/em>(next to beeps and time) in the Client activity window and clicking on the icons in the upper left corner (indicated by the red square in the figure below). Only the items that are visualized in the table are exported. Apart from the answers, the export contains the date and time each interaction was completed.<\/p>\n\n\n\n

\"\"
Click on the green icons to copy or export the data of an individual participant.<\/figcaption><\/figure>\n\n\n\n

Export a larger dataset for statistical analysis<\/h3>\n\n\n\n

Advanced export requires a Premium account<\/a>.<\/p>\n\n\n\n

If you have a premium account, there is an extra Export tab in the main menu, just below the Settings tab. Here you can download .csv<\/strong> files of multiple participants at once. Make sure your browser window is big enough or the option might be hidden. In the Export tab, several options can be set before you proceed to export the data:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
Export from<\/h5>\n\n\n\n

Here you can chose from which account(s) you want to export data, in case your participants are sharing data from other accounts with you. In most cases you only want data from this account.<\/p>\n\n\n\n

Interactions<\/h5>\n\n\n\n

Here you can choose if you want to export all interactions\/questionnaires or just a selection.<\/p>\n\n\n\n

Exported data structure<\/h5>\n\n\n\n

The exported data files will be .csv<\/strong> files. All data files use the semicolon character as a delimiter and have the same basic structure: every row (except for the first) represents an interaction (questionnaire) that was sent to\/completed by a participant and the data collected in that interaction is organized in the cells of that row.<\/p>\n\n\n\n

This typically results in one row per scheduled beep: if the beep was completed, the row contains the answer data; if the beep was not completed, the row only contains the meta-data of the originally scheduled beep. Missed reminders don’t generate extra rows. If the \u2018One time answer\u2019 property was not enabled in a scheduled beep’s properties, it is possible to have more rows for that beep because participants would be able to press \u2018REPEAT QUESTIONNAIRE\u2019 in the home screen of the app and generate extra answer rows for the same beep. Repetitions like this would have the same sentBeepId\/reminderForOriginalSentBeepId (see table below).<\/p>\n\n\n\n

The first columns contain the meta-data of the interaction and are explained in the table below.<\/p>\n\n\n\n

connectionId<\/strong><\/td>unique number for each participant in the context of this m-Path account<\/td><\/tr>
legacyCode<\/strong><\/td>legacy invitation code with which participant originally enrolled<\/td><\/tr>
code<\/strong><\/td>invitation code with which participant originally enrolled<\/td><\/tr>
alias<\/strong><\/strong><\/td>nickname the participant has chosen at this moment in time<\/td><\/tr>
scheduledBeepId<\/strong><\/strong><\/td>unique number identifying each scheduled instance of an interaction, -1 indicates an intake interaction, 0 indicates a non-scheduled interaction (test on client, …)<\/td><\/tr>
sentBeepId<\/strong><\/strong><\/td>unique number identifying each interaction that is sent<\/td><\/tr>
reminderForOriginalSentBeepId<\/strong><\/strong><\/td>if this interaction is initiated by a reminder, this number is the sentBeepId of the original (missed) interaction<\/td><\/tr>
questionListName<\/strong><\/strong><\/td>tab name of the interaction\/questionnaire<\/td><\/tr>
timeStampScheduled<\/strong><\/strong><\/td>time stamp (unix time, see https:\/\/en.wikipedia.org\/wiki\/Unix_time<\/a>) the notification was scheduled for.
Converting this timestamp under the assumption of a UTC time zone will generate the local date\/time on the phone. This way timestamps of different time zones are comparable in terms of daily rhythm.<\/td><\/tr>
timeStampSent<\/strong><\/strong><\/td>time stamp the notification was sent<\/td><\/tr>
timeStampStart<\/strong><\/strong><\/td>time stamp the interaction started (questionnaire was opened)<\/td><\/tr>
timeStampSto<\/strong>p<\/strong><\/td>time stamp the interaction was completed (questionnaire was finished)<\/td><\/tr>
originalTimeStampSent<\/strong><\/strong><\/td>in case of reminders, time stamp of the original interaction<\/td><\/tr>
timeZoneOffset<\/strong><\/strong><\/td>the offset in seconds from UTC time<\/td><\/tr>
deltaUTC<\/strong><\/td>the difference in seconds between UTC time as measured on the participant’s phone and on our servers. This can account for small discrepancies in timeStampStart and timeStampStop, which are based on the phone’s internal clock. If deltaUTC is larger than a couple of seconds, it can be indicative of participants tampering with their phone’s time settings to circumvent expiration times.<\/td><\/tr><\/tbody><\/table>
First columns of each export file<\/figcaption><\/figure>\n\n\n\n

<\/p>\n\n\n\n

The later columns refer to the actual interaction items. The column titles are a combination of the item label<\/mark> and the corresponding question type<\/mark>: label<\/mark>_type<\/mark>. In contrast to other question types, each multiple choice question has three corresponding columns:<\/p>\n\n\n\n

label<\/mark>_multipleChoice_index<\/mark>: index of the choice made (1 is first) <\/p>\n\n\n\n

label<\/mark>_multipleChoice_string<\/mark>: text of the choice made<\/p>\n\n\n\n

label<\/mark>_multipleChoice_likert<\/mark>: designated likert value<\/a> of the choice made<\/p>\n\n\n\n

In case the same label<\/mark>_type<\/mark> combination was filled in multiple times (e.g., because item labels were not unique during the same interaction), extra columns are added: the first repetition of the column title is extended with _1, the second with _2, etc.<\/p>\n\n\n\n

Timestamps<\/h5>\n\n\n\n

The file includes multiple time stamps (e.g. timeStampSent). As explained in the table above, they are in unix time, also known as seconds since epoch. To transform the timestamp to a readable time in R, you can use the following function (potentially you first need to import tidyverse):<\/p>\n\n\n\n

# install.packages(\"tidyverse\")\nlibrary(tidyverse)\ntimestamp <- 1699267982\ntimestamp |> as_datetime() |> force_tz(\"Europe\/Brussels\")<\/code><\/pre>\n\n\n\n
Here the timestamp is 1699267982 . R has the following output: “2023-11-06 10:53:02 CET”<\/em>. The time zone is forced to ‘Europe\/Brussels’ which was the time zone of the participant in this case.<\/p>\n\n\n\n
Types<\/h5>\n\n\n\n
Here you can choose which types of data you want to download. For every type of data selected, a separate .csv file will be downloaded.<\/p>\n\n\n\n
Basic data file<\/h6>\n\n\n\n
In the basic data file, the non-empty cells in the label<\/mark>_type<\/mark> columns contain the actual item responses of participants. The empty cells pertain to items that were not filled in in that row’s interaction (e.g., questions that were not asked in that interaction). Basic data also includes rows for interactions that were sent but not completed. They are appended at the end of the file and do not contain further data.<\/p>\n\n\n\n
Order data file<\/h6>\n\n\n\n
Sometimes the order in which items (questions) are presented is not fixed, e.g., when using the randomization features of container items. In this case, you may still want to know the order in which they were presented. In this export file, every relevant response cell contains a number: 0 means this item was the first item encountered in this interaction, 1 means it was the second item encountered, and so on.<\/p>\n\n\n\n
Skipped data file<\/h6>\n\n\n\n
For those items that had the skipped option enabled, it is necessary to know if this option was used. In this export file, items that have been skipped have the value 1.<\/p>\n\n\n\n
Response time data file<\/h6>\n\n\n\n
In this export file, every item response cell contains the time (in ms) it took the participant to fill in that item. <\/p>\n\n\n\n
Importing data in a statistical software package<\/h2>\n\n\n\n
Once the data is downloaded as a .csv file using premium export<\/a>, the resulting file can be imported into any statistical software package. For R, a package exists to make this process even easier:<\/p>\n\n\n\n
\n
R package for importing m-Path data<\/a><\/div>\n<\/div>\n\n\n\n
There is also a possibility to import your.csv file in Excel, but we do not recommend exporting data this way. The best way to process the data is in R<\/strong> or another statistical program like SPSS, Matlab,…. But if you do really wish to import it in Excel, we have a few tips and tricks on how to do it<\/a>.<\/p>\n\n\n\n
Referencing m-Path<\/h2>\n\n\n\n
If you use m-Path data in a publication, feel free to reference m-Path<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
There are two ways of exporting data from your dashboard: single participant export in the Visualize tab, or advanced export of a larger dataset for statistical analysis in the Export tab (available for premium subscriptions only). Export plain data of a single participant You can export a very simple representation…<\/p>\n","protected":false},"author":3,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":{"footnotes":""},"ht-kb-category":[63,349],"ht-kb-tag":[463,303],"class_list":["post-9018","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-data-collection","ht_kb_category-visualize","ht_kb_tag-data","ht_kb_tag-export"],"_links":{"self":[{"href":"https:\/\/app-manual-wp-001-atfsdabuggg7fzdq.germanywestcentral-01.azurewebsites.net\/wp-json\/wp\/v2\/ht-kb\/9018","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/app-manual-wp-001-atfsdabuggg7fzdq.germanywestcentral-01.azurewebsites.net\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/app-manual-wp-001-atfsdabuggg7fzdq.germanywestcentral-01.azurewebsites.net\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/app-manual-wp-001-atfsdabuggg7fzdq.germanywestcentral-01.azurewebsites.net\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/app-manual-wp-001-atfsdabuggg7fzdq.germanywestcentral-01.azurewebsites.net\/wp-json\/wp\/v2\/comments?post=9018"}],"version-history":[{"count":29,"href":"https:\/\/app-manual-wp-001-atfsdabuggg7fzdq.germanywestcentral-01.azurewebsites.net\/wp-json\/wp\/v2\/ht-kb\/9018\/revisions"}],"predecessor-version":[{"id":15604,"href":"https:\/\/app-manual-wp-001-atfsdabuggg7fzdq.germanywestcentral-01.azurewebsites.net\/wp-json\/wp\/v2\/ht-kb\/9018\/revisions\/15604"}],"wp:attachment":[{"href":"https:\/\/app-manual-wp-001-atfsdabuggg7fzdq.germanywestcentral-01.azurewebsites.net\/wp-json\/wp\/v2\/media?parent=9018"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/app-manual-wp-001-atfsdabuggg7fzdq.germanywestcentral-01.azurewebsites.net\/wp-json\/wp\/v2\/ht-kb-category?post=9018"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/app-manual-wp-001-atfsdabuggg7fzdq.germanywestcentral-01.azurewebsites.net\/wp-json\/wp\/v2\/ht-kb-tag?post=9018"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}