Understand the flow of a survey when exporting survey questions through API

Hi @Rod_Pestell! The typical best practice to tracking progress through the survey is to use embedded data fields to capture certain points along the way (screenshot 1). ! However, as you have pointed out, this won't work for surveys using the Table of Contents feature where a respondent can skip from section to section. In this case, I would recommend adding Javascript to each question that will keep track of a respondent's path through the survey by appending the question number to a string stored in an embedded data variable. This will keep track of each question the respondent sees in their path through the survey (screenshot 2, 3). ! ```javascript Qualtrics.SurveyEngine.addOnload(function() { //Javascript for splitting Time/Focus on Site var path = "${e://Field/javascriptSurveyPath}"; var updatedPath = path + "," + "Q1" Qualtrics.SurveyEngine.setEmbeddedData('javascriptSurveyPath', updatedPath); }); ``` The result is a list of values in the data set that can be used to derive the path taken through the survey (screenshot 4). In the example below, I completed the survey twice using different paths through the Table of Contents. ! Let me know if you have any questions. I hope that helps!

@KierJ, Thanks for the reply. I'll look into that but for a survey that is 100 questions or have even 200 questions that might be quite time consuming in adding all the java script. I guess the JavaScript could be made generic and record the QID. So from the example "Start,Q2,Q3,Q4,Q5", you would know that the predecessor of Q5 was Q4 and also how many times Q4 was visited. Do you think this code could be placed and made to work from the look and feel header? Thanks Rod

@Rod_Pestell that's a lot of survey questions! I've never tried what you're suggesting. Totally a guess, but my hunch is that it wouldn't work because the Look and Feel might be rendering separately from the survey flow logic.