Other Tools on the Report Page
Filter: Looped questions can be used in Report Page filters. When a looped question is selected as a reference question, users must specify which loop iteration the filter should be based on.
In the example below, Shopping Experience is a looped question asked across three stores (i.e. loops). If a user wants to filter respondents who selected “Somewhat satisfied” or “Very satisfied” for Harvest Mart, they can select Harvest Mart as the loop iteration to apply the filter
In the example below, the user can choose to display answers to Shopping Experience from the Harvest Mart loop.
Analysis Variable: Looped questions can be used to create Analysis Variables. When defining Analysis Variables, users can currently apply rules only across all loops; we currently don't support creating separate Analysis Variables for individual loop iterations.
In the example below, if users want to create an Analysis Variable showing the Top 2 results for Shopping Experience, the same rule must be applied across all stores (i.e., all loops).
However, when using this Analysis Variable as a filter, users can specify which loop iteration the filter should be based on.In the example below, the user can choose to filter on Top 2 selections from the Shopping Experience T2 Analysis Variable in the Harvest Mart loop.
PowerPoint Export: When exporting the report to PowerPoint, the export reflects any filters applied on the dashboard Report Page. Page-level filters are clearly shown on the PowerPoint cover page, and loop filters appear next to the sample size for each looped question.
In the example below, if users select the Harvest Mart loop for Shopping Experience on the Report page, the PowerPoint export will display the Harvest Mart results on the corresponding slide, with the loop name shown next to the sample size.
For each Crosstab tab or sheet, users should first select whether they want to work with Standard (Respondent Level) data or Stacked (Loop Level) data for their analysis. By default, the Crosstab runs on Standard (Respondent Level) data. However, if users want to analyze differences of a looped question across loops, they should switch to Stacked (Loop Level) data.
To compare shopping experience across Harvest Mart, PurePick, and The Green Mart, users should switch to Stacked (Loop Level) data. They should then select Shopping Experience (which stacks responses from all loop iterations) as the Stub and Brand Based Loop (which indicates the loop iteration for each data row) as the Header.
Please note that changing the data level on the Crosstab tab will remove any headers, stubs, and filters applied at the current data level on that tab. To keep these settings, users should open a new tab to view analysis results at a different data level.
Standard (Respondent Level) - default export
For example, in the case below, Shopping Experience is a question within the Brand-Based Loop, which includes three loops: Harvest Mart, PurePick, and The Green Cart. From the data file, we can see that Respondent ID 1358065 was shown Harvest Mart first, followed by The Green Cart. This respondent answered “Somewhat satisfied” for Shopping Experience for Harvest Mart, and “Very satisfied” for The Green Cart.
Stacked (Loop Level)
Loop level data differs from our current respondent-level structure. Instead of one row per respondent, the data is restructured so that each participant has multiple rows - one for each loop iteration they were shown. An additional column is added to indicate which loop option each row corresponds to. If the loop includes a single-choice Question A with three loop iterations (Loop 1, Loop 2, and Loop 3), the data file will contain only one column for Question A. If Respondent 1 is shown the loop 2 and 2, their data will appear in two separate rows - one for each loop iteration - with a new column called CurrentLoop specifying whether the row is for Loop 1 or Loop 2. In addition, the order in which loops were presented to participants will be captured in a column called LoopPosition.