QSM Reporting And Analysis - WordPress Plugin

Guide to Setting Up and Using QSM Reporting And Analysis

QSM Reporting And Analysis is not for creating quizzes themselves. It is for working with what happens after users submit their answers: submissions, scores, points, completion rate, question results, category points, and period-over-period comparisons. In this guide, we will walk through how to install and validate the add-on, which reports to build first, how to avoid mixing quiz and survey data, how to display charts on the result page, and how to troubleshoot cases where graphs or metrics do not look the way you expected.

This article is intended for a site owner, instructional designer, marketer, HR specialist, or developer who already uses Quiz and Survey Master and wants to make decisions based on data rather than simply review individual records in the results section. We will not cover purchasing, payment, or license delivery. What matters here is the working model: where the add-on appears in the WordPress admin area, which filters change the data set, which metrics depend on the form type, why older sites may need a database migration, and how to safely validate chart output on the public-facing side of the site.

This guide uses the exact names of QSM and WordPress interface items, so some English labels remain as QSM, Reporting & Analysis, Apply Filters, Create Chart, Save, and template variables. The rest of the explanations are written as plain-language guidance so the article reads like a practical tutorial rather than a retelling of the documentation.

What This Add-On Helps You Do After Responses Are Collected

The standard results section in QSM is useful when you need to open a specific submission and see who responded, how many points the user earned, how long the quiz took, which contact fields were filled out, and which answers were selected. That is the record level. QSM Reporting And Analysis adds the next layer - an analytics view where the focus is not on individual attempts, but on patterns across a group of responses.

In practice, that changes how you work with a quiz. Without a reporting layer, an administrator often downloads a CSV, filters the table manually, builds charts in a third-party tool, and returns to WordPress only to verify the source record. With the reporting add-on, some of those questions can be answered directly inside the site: how many submissions came in during the selected period, how the average score changed, which quizzes generate more submissions, where users most often leave questions unanswered, which category is underperforming, and which answer labels deserve closer analysis when Advanced Assessment is enabled.

The add-on is most valuable when a quiz or survey runs continuously. A one-time feedback form after a single event can be handled manually. But if your site collects course assessments, certification tests, customer surveys, lead-generation quizzes, or recurring employee evaluations, the administrator needs more than a list of records - they need a repeatable system for analysis. The real purpose of QSM Reporting And Analysis is to move quickly from raw submissions to conclusions you can verify and reproduce through a saved report.

How reports differ from standard results review

In QSM Results, you see submission details: quiz name, score, points earned, time to complete, contact fields, user id, IP address, and answers. That works well for auditing a specific user or manually reviewing a disputed attempt. Reporting And Analysis gives you the aggregated view instead: summary stats, charts, top performing quizzes, filters, custom reports, and charts for individual questions or categories.

The difference becomes especially clear in three situations. First, comparing periods. If you need to know whether results improved after a course update, a simple list of records is not enough. Second, working with multiple quizzes. When your site has an introductory quiz, a final exam, and a satisfaction survey, reporting helps you look at them as a system. Third, explaining the outcome to the user. With template variables, you can place a pie or bar chart directly on the result page so the participant sees not only their score, but also the answer distribution or category contribution.

When this product may be unnecessary

The add-on is not necessary for every site running QSM. If you have one simple quiz, a few attempts per month, and no need to compare periods, the standard QSM Results and, if needed, Export Results are enough. Reporting And Analysis also does not replace a full BI system if your team builds complex reporting across external CRM data, an LMS, ad campaigns, financial data, and user segments outside WordPress.

Another limitation is the quality of the underlying quiz. Charts will not fix poorly designed questions. If questions are not grouped into categories, answer options are worded inconsistently, the score does not reflect the actual grading model, or a survey is mixed with an exam, the reports will simply produce attractive graphs on top of a weak data model. That is why the right starting point is not the chart, but the question: what decisions are you going to make based on this data?

What to Prepare Before Installing It on a Live Site

Before installing the reporting add-on, check more than just the plugin file itself. You should also verify the state of QSM. Reporting And Analysis depends on data already created by Quiz and Survey Master: submissions, result records, question categories, answer labels, points, scores, user information, and result page templates. The more carefully the main form is configured, the less manual interpretation you will need later in your reports.

Start with this checklist. It is short, but it saves a lot of time during troubleshooting:

• Make sure the main Quiz and Survey Master plugin is active and your quizzes are actually receiving submissions.
• Verify that WordPress has an administrator role or another role with sufficient permissions to manage QSM and view results.
• Open QSM - Results and confirm that new attempts appear in the list.
• If the site has used QSM for a long time and has not yet migrated to the new data structure, create a database backup first and review the migration section.
• If you need category-based reporting, assign categories to questions ahead of time. Without that, category filtering will not give you useful analytics.
• If you plan to analyze by users or user groups, decide whether participants must be logged in before taking the quiz.
• If charts will be shown to users on the result page, decide in advance which questions and categories are actually safe to expose to participants.

A critical check before deploying on a production site: submit a test response, open it in QSM - Results, then confirm that the same submission appears in the reporting dashboard after applying a filter for the current period. If the record is not visible even at this level, troubleshoot the core QSM results flow first, not the charts.

A special case for sites after a QSM update

For older installations, the QSM database migration matters. In the newer QSM branch, both the quiz display model and the result storage structure were redesigned. The documentation describes a one-time migration wizard that checks add-on compatibility, shows progress, and preserves existing quizzes, data and results. This matters for Reporting And Analysis because the new dashboard depends on the updated data structure.

If, after updating QSM, you see a message in the old Results - Reporting & Analysis section about the new dashboard and a prompt to migrate, do not ignore it. Back up the database first, verify compatibility for the installed QSM add-ons, run the migration wizard, and let it finish completely. Do not close the migration page or refresh the browser tab until the process is complete. After that, the new QSM - Reporting & Analysis menu item should open directly from the QSM sidebar.

Data worth normalizing in advance

Reports become much more useful when you have consistent naming and category discipline. If one test is named "Final exam," another "Final test," and a third "Exam final copy," and question categories are duplicated with different spellings, the dashboard will still show data, but the meaning will become fragmented. Before using the add-on actively, it helps to clean up:

• Quiz and survey names, so reports are easier to read.
• Question categories, especially for training, certification, and professional assessments.
• Form type: quiz for graded evaluation with score/points, and survey for collecting opinions without grading.
• Contact fields, if reports will be reviewed not only by anonymous attempts but also by user identity.
• Result pages, if you plan to display charts there.

This step does not require code. It requires a clear understanding of what story the data should tell. For example, an e-learning portal benefits from categories such as "Theory," "Practice," "Safety," and "Common Mistakes." Then category charts reveal not just the overall score, but the weak point in the course. For a customer survey, categories like "Usability," "Support," "Pricing," and "Features" make more sense.

Installation and First-Time Activation Without Unnecessary Risk

Reporting And Analysis is installed like a standard WordPress plugin add-on for QSM. In the WordPress admin area, open Plugins - Add New, choose Upload Plugin, upload the add-on ZIP file, and activate it. After activation, QSM - Reporting And Analysis should appear in the plugin list, and a tab or menu item related to Reporting and Analysis should appear in QSM settings.

If you use the QSM add-ons flow inside the QSM panel itself, the documentation shows this path: Extensions - QSM - Installed, then the Reporting and Analysis card, the Settings button, and the License tab. That is where you enter the license key, along with the Limit Chart/Question Title Text setting. By default, it limits chart question title length to 100 characters, which is helpful for long question text.

After saving settings, open QSM - Reporting & Analysis. If the dashboard loads correctly, you will see an overview of quizzes, surveys and tests, the Date Range filter, period comparison via Compare, summary cards, and charts. On first launch, do not try to configure everything at once. First, confirm that the selected period actually contains submissions and that the numbers match what you expect from the standard results section.

Quick validation after activation

1. Create or choose a test quiz that is already published on a page.
2. Complete it as a regular user or in a separate browser without your admin session.
3. Open QSM - Results and make sure the new record is there.
4. Open QSM - Reporting & Analysis, select a period that includes the test submission, and click Apply Filters.
5. Compare the submission count, average score, and average points with what you expect from the test record.

If the submission exists in Results but not in the reporting dashboard, check the date range, database migration, selected quiz, and any saved filters. If there is no record even in Results, the issue is not Reporting And Analysis but the core QSM submission flow: the page, submit button, required fields, caching, theme conflict, or a JavaScript error.

What not to do on first launch

Do not start making broad conclusions from old data until you have validated one fresh test example. Do not enable every chart on the result page until you have chosen a specific question and understand exactly what the user will see. Do not treat surveys and quizzes as identical entities: for surveys, some score/points metrics may be unavailable or simply meaningless. And do not give editors or managers access to reports without understanding what personal data may be included in the results.

Check updates as well. The add-on changelog includes fixes related to CSV/PDF endpoint access, nonce/capability checks, SQL injection in handlers, shortcodes, and result filters. That is not a reason to panic, but it is a direct argument for keeping your license active, installing patches promptly, and restricting access to analytics data to the roles that actually need it.

Your First Dashboard: Metrics, Filters, and Hidden Pitfalls in Reading the Data

The main Reporting And Analysis dashboard gives you a quick view of quiz and survey performance. The top section helps you choose a period and comparison mode, followed by summary stats, charts, and a list of top performing quizzes. At first glance, it looks like standard analytics, but there are important nuances: a metric changes meaning depending on the form type, period comparison does not explain why the change happened, and a polished chart can hide a sample that is simply too small.

The Date Range filter

Date Range determines which submissions are included in the dashboard. The documentation mentions preset options such as Last Week, Last Month, Week to Date, and a custom date range. In day-to-day work, that means you can quickly compare the first week of a course launch, a post-email campaign period, or the time after changing your questions.

A common beginner mistake is to look at "all data" and conclude that the quiz is performing well or poorly. If the quiz has changed over time, a lifetime data set will mix the old and new versions together. It is better to define a period around a specific change, such as before and after revising a difficult block of questions. The same average score can mean very different things if the sample mixes different quiz versions, different audiences, and different traffic sources.

Compare: previous period or previous year

The Compare setting lets you compare the selected date range with the previous period or the previous year. This is useful when you want to see a trend, but you should not treat a percentage change as a final conclusion. If submissions increased, the reason could be an email campaign, a new page, paid traffic, seasonality, or a change in quiz difficulty. If average completion rate dropped, the cause could be a longer form, a required field, a mobile issue, a theme conflict, or a more difficult audience.

A practical workflow looks like this: first choose the period and comparison mode, then review the summary cards, then look at the charts, and only after that open individual results if you need to validate specific attempts. That way, you are not arguing with a number in the abstract. You are tracing a cause-and-effect chain: what changed in the form, the users, the questions, or the page.

Summary Stats

The dashboard uses key metrics such as total submissions, unique users, average completion rate, average time, and other values depending on your data and active extensions. In custom reports, the set is broader: total submissions, average score, average points, average completion rate, average correct answers, average incorrect answers, average unanswered questions, and average time. For a survey with no grading, score and points may be disabled, which makes sense - a survey does not have to contain correct answers.

The most useful insight usually comes not from a single card, but from a pair of metrics. For example, high submissions with low completion rate points to a completion problem, not weak demand. High average time and many unanswered questions may mean a question is difficult, unclear, or performs poorly on mobile widths. Average score without category data gives you a general level, but it does not show which knowledge area is underperforming.

Top Performing Quizzes

The top performing quizzes table ranks quizzes by submissions and shows quiz name, submissions, average score, and average points. This is helpful for a portal with multiple tests: you can quickly see which materials users actually complete and which ones rarely get opened. But "top performing" does not always mean "most valuable." An introductory entertainment quiz will usually get more submissions than a final exam. When making decisions about course quality, look not only at volume, but also at score, completion, time, and category-level weak spots.

In the upper-right corner of the dashboard, there are section visibility settings: you can hide overview, charts, performance, recent activity, and my reports. This does not affect the underlying data, but it does help keep the workspace cleaner. For example, an instructional designer may need charts and performance, while a project lead may only need overview and top performing quizzes.

Custom Reports: How to Build a Report for a Specific Goal

Saved reports are one of the most practical parts of QSM Reporting And Analysis. They let you define the right data set once, save it, return to it later, duplicate it, and adapt it for another question. That matters more than it may seem: good analytics is built on a repeatable method, not on randomly opening a chart.

In the documentation, the workflow starts with the View Reports button on the dashboard. In the reports section, click Add New, enter a report name, and save it. That opens a dedicated report dashboard with filters, summary stats, and charts. Each report includes actions such as Edit, Duplicate, Save, and Delete. If you leave without saving, the interface warns you about unsaved changes.

How to name a report so it is still useful next month

Do not call a report "Test report" or "Analytics." The name should capture the management question behind it. For example:

• "Final Exam - Category-Level Mistakes"
• "Customer Survey - Responses by User Group"
• "Intro Quiz - Submissions After Email Campaign"
• "Certification - Average Time and Unanswered Questions"
• "Assessment Labels - Answer Type Distribution"

This approach does more than make reports easier to find. It also forces discipline in how you configure filters. If a report is named "category-level mistakes," it should include categories and a category chart, not a random overall submissions graph.

Filters inside a custom report

A custom report can use filters for quizzes, categories, users/groups, date range, and compare. If you select surveys only, the documentation lists a limited metric set: total submissions, average time, average completion rate, and average unanswered questions. If you select quizzes or a mix of quizzes and surveys, summary stats shows a more complete metric set.

This distinction is important. A survey answers the question "what did people choose or write," while a quiz also answers "how accurately or successfully did they complete the assessment." That is why average score and average points should not be forced into reports where the form does not actually grade correctness.

The three dropdowns when creating a chart

A chart inside a custom report is created via the + button. You then choose what to analyze: questions, categories, users, or answer labels if Advanced Assessment is installed. The second choice defines the metric: responses, average points, or average score. The third narrows the focus to a specific question, category, or user. After clicking Create Chart, the chart is added to the report dashboard.

The purpose of these three dropdowns is not simply to "add a graph." It is to connect the reporting question to the right visual form. If the goal is to find the weakest topic in a course, choose categories and average score. If the goal is to understand which answer option is chosen most often in a survey, choose questions and responses. If the goal is to evaluate group progress, filter by users/groups and look at score/time within the appropriate period.

Core Product Mechanics: From Question to Chart, Report, and Visible Outcome

Reporting And Analysis includes several mechanics that set it apart from a simple results list. It helps to think of them as chains: where the user enters the input conditions, how the add-on transforms the data, what appears on the output side, how to validate the outcome, and where the limitation lies.

Mechanic 1: Date Range + Compare

Where it is configured: the top of the dashboard or a custom report. User input: a preset or custom date range, plus the comparison mode. How the product works: the add-on selects submissions for that period and shows the change relative to the previous period or previous year. Visible outcome: cards and charts showing the trend. Validation: the number of submissions should match the expected number of submissions for the selected period. Failure symptom: the report is empty or the trend looks impossible. Safe fix: widen the date range, remove extra filters, and check the date of the test submission in QSM - Results. Limitation: comparison shows that something changed, but not why, unless you validate the surrounding context.

Mechanic 2: a saved custom report

Where it is configured: Reporting & Analysis - View Reports - Add New. User input: report name, selected quizzes, categories, users/groups, period, and charts. How the product works: the report saves the configuration so you can return to it without rebuilding it from scratch. Visible outcome: a dedicated dashboard with its own filters, summary stats, and charts. Validation: close the report, reopen it from the reports list, and confirm that the structure was preserved. Failure symptom: after changes, the report does not reflect the new configuration. Fix: click Save, do not close the page when warned about unsaved changes, and use Duplicate before experiments if needed. Limitation: a saved report does not improve the quality of your underlying categories or score model.

Mechanic 3: chart configuration

Where it is configured: the charts section, using the + button or the graph icon next to the chart name. User input: analysis dimension, metric, and the specific object. How the product works: the data is split across the selected axis and displayed as a pie, line, filled line, or bar chart. Visible outcome: a custom chart on the dashboard. Validation: the chart should answer a specific question, not just "look good." Failure symptom: score/points are disabled for a survey. Fix: choose responses instead, or work with a quiz that actually has score data. Limitation: a chart does not replace raw result details when you need to investigate a specific attempt.

Mechanic 4: result page variables

Where it is configured: the result page template in QSM. User input: a template variable such as %QSM_PIECHART_RESULT_X%, %QSM_BARCHART_RESULT_X%, %CATEGORY_POINTS_PIECHART%, or %CATEGORY_CONTRIBUTION_BARCHART%. How the product works: after submission, QSM replaces the variable with a chart on the result page. Visible outcome: the user sees a graph showing answer distribution or category contribution. Validation: complete the quiz as a user and open the result page after submitting. Failure symptom: the variable appears as text, the chart is empty, or it does not match the question. Fix: confirm that X has been replaced with a real Question ID, that the question is multiple-choice for a question-level chart, and that categories/points are configured anywhere a category chart is used. Limitation: question-level pie and bar charts are supported for multiple-choice questions.

Mechanic 5: working together with Advanced Assessment

Where it is configured: the QSM Advanced Assessment add-on and the chart dropdown inside Reporting And Analysis. User input: labels assigned to answers and an enabled assessment. How the product works: answer labels become an additional analytics axis available in reports when Advanced Assessment is installed. Visible outcome: you can analyze not only correctness, but also the distribution of answer types. Validation: labels must be assigned to answer options, and the report should show the Answer Labels option. Failure symptom: the labels option is unavailable. Fix: check whether Advanced Assessment is active, verify assessment settings, and confirm that labels have been assigned. Limitation: labels are only useful when they are intentionally designed in advance, such as for personality quizzes or psychometric tests.

Displaying Charts on the Result Page

The most visible Reporting And Analysis feature for visitors is result page charts. This is not just decoration. A chart can help the participant understand their outcome in context: how answers were distributed for a question, how many points they earned across categories, or which category contribution shaped the final score. But charts should be exposed carefully, because a public result page may be personal, instructional, or marketing-oriented.

The official documentation lists several template variables. For question-level charts, use variables with a Question ID: %QSM_PIECHART_RESULT_X% and %QSM_BARCHART_RESULT_X%, where X is replaced with the question ID. For category points, use %CATEGORY_POINTS_PIECHART% and %CATEGORY_POINTS_BARCHART%. For category contribution, use %CATEGORY_CONTRIBUTION_PIECHART% and %CATEGORY_CONTRIBUTION_BARCHART%.

%QSM_PIECHART_RESULT_X%
%QSM_BARCHART_RESULT_X%
%CATEGORY_POINTS_PIECHART%
%CATEGORY_POINTS_BARCHART%
%CATEGORY_CONTRIBUTION_PIECHART%
%CATEGORY_CONTRIBUTION_BARCHART%

The important point here is not to paste every variable at once. Choose one chart that strengthens the outcome. For an educational test, a category points chart makes sense: the participant sees which topics earned more or fewer points. For a marketing survey, question-level distribution may be useful if you want to show how the participant compares with the broader response set. For an assessment with categories, a contribution chart explains which block had the strongest impact on the final outcome.

How to safely add a question-level chart

1. Open the quiz in QSM and find a question whose answer distribution is actually worth showing.
2. Confirm that it is a multiple-choice question, because the documentation limits question-level pie and bar charts to that type.
3. Find the Question ID and replace X in the variable, for example %QSM_PIECHART_RESULT_12%.
4. Open the result page template and place the variable next to a short explanation of what the chart shows.
5. Save the result page, complete the quiz as a user, and confirm that the chart appears after submission.

Do not show users internal analytics without a clear purpose. If the chart does not help explain the result, it is better left in the admin report. The result page should contain only charts that clarify the answer, category, or next step.

Category contribution without manual math

A category contribution chart shows each category's share of total earned points. The formula in the documentation is straightforward: category points are divided by total earned points and multiplied by 100. In practice, this is useful for assessments where you need to explain the profile behind the outcome. For example, a user earns points in three categories, and the result page shows which area contributed most strongly to the final result.

For this to work, questions must have categories and answers must award points. If categories are missing or points do not reflect the actual scoring model, the contribution chart may render correctly but still do a poor job explaining the outcome. That is why, before exposing it publicly, you should validate the category mapping and one test flow with known answers.

A custom CSS tweak for a cleaner result block

QSM officially supports Custom Style CSS in the Style tab, and the documentation lists public classes such as qsm-quiz-container, qsm-quiz-form, qsm-error-message, and others. If a chart on the result page gets visually lost in the surrounding text, you can add a small, reversible CSS snippet in the custom CSS field for that specific quiz. This is a custom adaptation based on QSM's officially documented custom CSS mechanism, not a hidden add-on hook.

.qsm-quiz-container .qsm-report-note {
  padding: 16px;
  margin: 18px 0;
  border: 1px solid #d8e2ef;
  border-radius: 8px;
  background: #f8fbff;
}

.qsm-quiz-container .qsm-report-note strong {
  display: block;
  margin-bottom: 6px;
}

To use this approach, wrap the explanation next to the template variable in the result page template in a block with the qsm-report-note class, if the QSM editor allows that HTML. Check the outcome after submission, then open the page in a private window. Rolling it back is easy: remove the CSS and remove the wrapper class from the result page template. If the theme or the QSM sanitizer strips custom HTML, do not try to work around it with scripts - just keep a simple explanation before the variable.

Practical Use Case: A Report for an Educational Quiz and How to Validate It

Imagine a WordPress learning site where QSM is used for a final test after a course. The goal is to understand which course topics cause the most mistakes, track changes after updating the materials, and show participants a clear category-based outcome. This use case highlights the strengths of QSM Reporting And Analysis because it brings together categories, a custom report, summary stats, a chart, and a result page variable.

Goal

You want a report called "Final Test - Topics With the Most Mistakes," and you want the result page to show a category points chart for the participant. The administrator should be able to see which categories are underperforming across the group, while the user should see how their earned points are distributed by topic.

Preparation

QSM should already have a published quiz with questions grouped into categories. Every question that affects the final outcome should use points. The site should have the main QSM plugin installed, Reporting And Analysis activated, and older data migrated if needed. For a basic test, you need at least one new submission, but for any serious conclusion, it is better to wait until the sample includes enough submissions for comparison.

Steps in the admin area

1. Open QSM - Reporting & Analysis and choose the period after the course update.
2. Click View Reports, then Add New, and enter a report name such as "Final Test - Categories."
3. In the Quizzes filter, select the final test.
4. In Categories, leave all training categories selected or choose one problem topic for a focused report.
5. In Date Range, set the period after the content change, and in Compare, choose the previous period if you want to see the trend.
6. Click Apply Filters and review the summary stats.
7. Add a chart: choose Categories, then the metric Average Score or Average Points, then refine by category or keep the breakdown that best fits the interface logic.
8. Save the report using Save.

After that, do not draw a conclusion based on a single graph alone. Open several individual results in QSM - Results and verify that the real answers match the picture shown in the report. If the chart shows a low average score for the "Practice" category, open a few attempts and see which questions caused the mistakes. That is what turns the dashboard into a course improvement tool rather than a decorative screen.

Adding a category chart to the result page

Next, add a visible outcome for the participant. Insert this variable into the result page template:

%CATEGORY_POINTS_BARCHART%

Before it, add a short explanation such as: "Below is how your points were distributed across the quiz topics." After saving, complete the quiz as a user and confirm that the chart appears on the final page. If you want to show contribution instead of raw category points, you can use %CATEGORY_CONTRIBUTION_PIECHART% or %CATEGORY_CONTRIBUTION_BARCHART% to display each topic's share of the final outcome.

Validating the outcome

Validation should happen on two levels. For the administrator: the custom report should show the selected quiz, period, categories, and expected metrics. For the participant: the result page should display the chart without raw template variables, without blank gaps, and without visual overlap with surrounding text. If, after completing the quiz, you see the literal string %CATEGORY_POINTS_BARCHART% on the result page, that means the variable was not processed in that location of the template or the add-on is not active for that use case.

A successful implementation is not "the chart appeared," but "the chart makes it obvious what should happen next." For a course, that may mean improving a weak topic. For an HR assessment, it may mean retraining in a particular category. For customer feedback, it may mean improving a specific part of the service.

Combined Workflows With Other QSM Add-Ons

Reporting And Analysis works well as the center of visual analysis, but it does not solve every data-related need by itself. The QSM ecosystem includes add-ons that complement it in meaningful ways: Export Results for CSV/PDF, Advanced Assessment for labels and psychometric logic, and Google Analytics Tracking for submission events in site analytics. The important thing is not to blur their responsibilities.

Export Results: when you need CSV or PDF

Export Results handles quiz result exports to CSV and PDF, field selection, date range, single row or separate row format, a PDF button for participants, and other tasks related to moving data beyond the reporting dashboard. Reporting And Analysis helps you spot patterns inside WordPress, while Export Results is for handing data off to an instructional designer, accounting team, client, external spreadsheet, or archive.

A practical workflow looks like this: first, use Reporting And Analysis to identify a question or category where there is a problem, then use Export Results to export the necessary fields for deeper review. The boundary is clear: Reporting And Analysis is for visual diagnosis and saved reports, while Export Results is for transferring records and documents. A common mismatch in expectations happens when someone looks for "export" inside Reporting And Analysis even though detailed export requires a separate add-on.

Advanced Assessment: labels as an additional analysis axis

Advanced Assessment lets you assign labels to answers, calculate label counts, label points, percentages, and build personalized results. In Reporting And Analysis, the presence of Advanced Assessment adds answer labels as an analysis option in custom charts. This is useful for personality quizzes, psychometric assessments, and any form where "right/wrong" does not capture the meaning of the answer.

The implementation order is straightforward: first design your labels, then assign them to answer options, then validate the assessment result page, and only after that build a chart by answer labels in the report. The risk is not technical but methodological: if labels are assigned inconsistently, the analytics will be inconsistent too. The validation step is to complete the test with a known answer set and confirm that the label-based result matches expectations.

Google Analytics Tracking: submission events vs. answer analysis

Google Analytics Tracking sends a quiz or survey submission event to Google Analytics. By default, the event uses category quiz, action submit, and a label based on the quiz name, while the settings let you enable tracking and modify category/action/label. This answers the question of how quiz interaction connects to site behavior: traffic sources, pages, conversions, and audiences.

Reporting And Analysis answers a different question: what exactly people answered, and how score, points, completion, and categories change. So the best combined workflow is this: use Google Analytics to see where users came from and how often they reach submit, and use Reporting And Analysis to see what outcomes they produced. That separation helps you avoid expecting QSM reports to explain behavior outside the quiz, or Google Analytics to provide a detailed answer-level breakdown.

Performance, Security, and Data Quality

The reporting add-on works with user results, so it should be treated as a tool with access to sensitive data. QSM Results may store name, email, phone, user id, IP address, page URL, and other fields if those options are enabled in the quiz. Reporting And Analysis aggregates this data, but it still sits close to personal result records. Access to reports should be restricted to roles that are actually allowed to see user results.

The add-on changelog shows that recent updates addressed security issues such as removing unauthenticated CSV/PDF endpoints, adding nonce and capability checks, fixing SQL injection in AJAX handlers, CSV exports, shortcodes, and result filters, validating PDF image data, and moving to the WP Filesystem API. For administrators, this leads to several practical rules:

• Do not leave an outdated add-on running on a production site, especially if you display charts via shortcodes or use exports.
• Do not hand out QSM administrative access to people who only need the final report.
• Check which personal fields the quiz collects, and do not expose them publicly through the result page.
• After updating the add-on, submit a test response and open the dashboard, a custom report, and a result page chart.
• If the site stores a large volume of submissions, test reports on a copy of the site or during a quiet period, especially after migration.

Large samples and slow reports

The Reporting And Analysis changelog includes an improvement for handling large data sets in reports. That is a good sign: the developers are paying attention to reporting-layer load. But administrators still need to design reports sensibly. If your site has thousands or tens of thousands of submissions, do not open all data at once unless you truly need to. Start with a limited date range, a specific quiz, and a specific category.

If a report loads slowly, check the sample size, the number of charts on the dashboard, period comparison, and the state of the database after migration. In many cases, it is better to create several focused saved reports than one huge report that tries to cover everything. That makes the work easier and reduces the risk of drawing the wrong conclusion.

When data should not be compared directly

Do not directly compare quizzes with different purposes. An introductory engagement quiz, a final exam, and a customer feedback survey produce different kinds of metrics. Even average time can mean different things: on an exam, a long completion time may be perfectly normal, while in a short lead quiz it may point to friction. Always add context to the report: the purpose of the form, the audience, the period, question changes, page changes, and traffic source.

Be especially careful with unique users. If the test is completed without login, uniqueness may be limited by what QSM can actually know about the user. If the quiz requires login, user/group filters become more useful, but the responsibility around access to personal data increases at the same time.

Troubleshooting Reports, Charts, and Result Issues

Most Reporting And Analysis issues are caused not by the chart itself, but by the data chain behind it: the submission was never created, the wrong period was selected, migration was not completed, the question type does not support the variable, the survey has no score, categories were never assigned, the user expects CSV export from a different add-on, or the result page strips the variable.

The dashboard is empty even though users completed the quiz

Symptom: QSM - Reporting & Analysis shows no submissions or the charts are empty. Possible cause: the selected date range does not include the submissions, extra filters are active, data from the older site was never migrated, the wrong quiz was selected, or the submissions never made it into QSM - Results in the first place.

What to check: open the standard QSM - Results, find a recent test record, and note its quiz name and time. Then, in Reporting And Analysis, widen the period, temporarily remove user/group/category filters, and click Apply Filters. If the site was updated from an older QSM structure, check the migration notice and the QSM - Tools - Migration section.

How to fix it: complete the migration, choose the correct period, verify the quiz selection, and create a new test submission. If the record does not appear in Results, fix the core quiz submission flow: required fields, submit button, JavaScript errors, page caching, or a theme conflict.

Average score or average points do not appear for a survey

Symptom: when creating a chart, some metrics are disabled. Possible cause: you selected a survey rather than a graded quiz. The documentation explicitly states that when a survey is selected, average points and average score may be unavailable.

What to check: the form type, whether score/points exist, and the underlying grading model. How to fix it: for a survey, analyze responses, completion, unanswered questions, and time; for score-based analysis, use a quiz with points configured. When to roll back the setup: if you started converting a survey into a quiz only to force score reporting, stop and reconsider the purpose of the form.

A template variable appears as plain text

Symptom: the user sees a string like %QSM_PIECHART_RESULT_12% instead of a chart. Possible cause: the variable was inserted into an unsupported result page template location, the add-on is not active, the variable was typed incorrectly, the Question ID is wrong, or the selected question type is unsupported.

What to check: whether QSM - Reporting And Analysis is active, whether the template variable is exact, whether the Question ID is correct, what question type is used, and what happens after a full quiz submission. How to fix it: replace X with the real ID, choose a multiple-choice question for question-level pie/bar charts, clear the result page cache, and complete the quiz again. If you need the variable in a PDF, also review Export Results settings, because PDF belongs to a separate add-on.

The chart appears on the result page, but explains the wrong thing

Symptom: the chart renders, but the participant does not understand how it connects to the final outcome. Possible cause: you selected a general question distribution instead of category points, the question categories do not align with the meaning of the result, or there are simply too many charts on the page.

What to check: what question the chart is answering, what next recommendation the user receives, and whether the chart reveals extra data it should not. How to fix it: keep only the most useful chart, add a short explanation, and switch from a question-level chart to category points or contribution if the goal is to explain the result profile. Rollback option: remove the variable from the result page and keep the analytics only in the admin dashboard.

The report shows a strange spike or drop

Symptom: submissions, score, or completion suddenly change. Possible cause: traffic changed, an email campaign went out, questions were updated, a different source became active, users started taking the quiz on mobile devices, or a required field or submit button introduced friction.

What to check: compare the date range with the previous period, open raw results, check the page URL, average time, unanswered questions, and recent site changes. How to fix it: split reports into periods before and after the change, create a separate report for the specific quiz, and test the page in a private window and at mobile width. If the cause is a theme or cache conflict, temporarily disable the suspicious optimization and repeat the test submission.

You need CSV, but Reporting And Analysis does not provide the export you need

Symptom: the administrator is looking for a table with fields, questions, answers, IP, page URL, category points, or a PDF for the participant. Possible cause: this is an Export Results task, not a Reporting And Analysis task. QSM has a separate add-on for CSV/PDF export with field selection and row format options.

What to check: whether Export Results is installed, which fields are needed, and whether you need single row or separate row output. How to fix it: use Reporting And Analysis to find the right sample, and use Export Results to move the data into an external spreadsheet or PDF. Do not build manual exports through direct database access unless you truly have no other choice.

How to Read Reports Without Fooling Yourself

Any analytics tool can create false confidence. QSM Reporting And Analysis displays charts, but the responsibility for interpretation still belongs to the administrator. A single chart may show that the "Security" category earned fewer points, but it will not tell you what is actually wrong: maybe the question wording is poor, the lesson is weak, the audience is new, the answer options are ambiguous, or the category combines unrelated topics.

A solid workflow for reading reports has four steps. First, define a hypothesis: "completion should increase after the lesson update," "the practice category should stop underperforming," or "the post-event survey should show fewer unanswered questions." Then choose the report and the period. Next, review the chart and summary stats. Only after that should you open individual results to inspect the actual answers.

The minimum set of questions to ask about every chart

• Are there enough submissions to support a conclusion, or are you looking at random noise?
• Are different versions of the quiz mixed into the same period?
• Did the traffic source, page, email campaign, or audience change?
• Does the metric actually fit the form type: quiz, survey, assessment, or feedback?
• Do the raw result details confirm what seems obvious from the chart?
• Is there a clear action after the conclusion: rewrite a question, split a category, shorten the form, change the result page, or check the mobile version?

This approach is especially important in client-facing and educational projects. A manager may see an average score drop and demand that the test be made easier, when the real cause is a new cohort of unprepared users. An instructional designer may see a high average time and conclude that the test is too difficult, when users are actually spending time reading long feedback blocks on the result page. A marketer may see many submissions and assume the quiz is successful, even though the completion rate and lead quality are weak.

When to create a separate report instead of relying on the main dashboard

Create a separate custom report if the question comes up repeatedly. For example, a monthly final exam review, a feedback survey analysis after every event, monitoring an employee onboarding quiz, comparing a user group, or watching one category over time. The main dashboard is great for a quick overview, but a saved report is what you need for recurring work.

Duplicating reports is useful for experiments. If you already have a report called "Final Test - All Categories," create a duplicate and narrow it down to one category or one user group. That way, you preserve the original working version and keep your comparison method intact. A report should answer one question; if it tries to answer five questions at once, it becomes harder to read and easier to misinterpret.

Tailoring Reports to Different Project Types

The same dashboard can be used in very different ways. Training portals, HR learning, marketing quizzes, and customer feedback surveys all care about different indicators, so it makes no sense to copy the same chart set into every report. QSM Reporting And Analysis gives you a general-purpose tool, but the quality of the outcome depends on how accurately you connect the project type to the right metrics and filters.

Before creating reports, it helps to map out a few basics: who will read the report, what question it must answer, what actions follow from the conclusion, and which data should never be shown publicly. If the reader is an instructional designer, they need weak categories, unanswered questions, and raw answers for disputed items. If the reader is a department lead, submissions, completion trends, and group dynamics matter more. If the report is embedded in the participant's result page, it should show only personal insight or safely aggregated meaning.

Training courses and online exams

For a training course, the core question is: "Which part of the material needs improvement?" Here, categories, average score, average points, average correct answers, average incorrect answers, and average unanswered questions are especially useful. If questions are divided into topics in advance, a custom report quickly shows whether the problem lies in theory, practice, terminology, calculations, or comprehension of the instructions.

The practical setup starts not in the report, but in the quiz structure. Divide questions into categories so each category maps to a real instructional block. Do not create an overly broad category like "General" if you later want to make course decisions based on it. After a few submissions, create a saved report for the final quiz, add a category chart, and compare periods. If a category score rises after a lesson update, validate the raw results: maybe the lesson became clearer, or maybe you accidentally made the grading easier.

For the result page in an educational flow, category points or a contribution chart is usually better than overall group response statistics. The participant needs to understand their profile: where they earned more points, where they need to review the material, and why the final outcome looks the way it does. If you add a recommendation after the chart, it should match the categories rather than repeating the same message for everyone.

Validating an educational report

Take one test attempt with known correct and incorrect answers. Open the raw result, verify the score and points, then open the report and the category chart. If the category chart does not reflect the expected outcome, do not look for a "chart bug" first. Look at category assignment, points, or question type. Until a test case can be reconciled manually, the report should not be used as a basis for course decisions.

HR assessment and employee training

In HR workflows, groups, recurring evaluation, and post-training comparisons are often important. Here, permissions and personal data need special care. If participants complete the quiz under WordPress user accounts, the users/groups filter can provide a helpful breakdown. But access to that report must be restricted, because it may reveal results for specific employees.

For this type of project, create separate reports: an overall progress report for the program lead, a category report for the instructional designer, and a limited result page for the participant. In the general report, you can track completion, average score, and time. In the instructional report, categories and question-level responses matter more. On the public result page, show only a personal chart or a carefully worded explanation of the outcome, without exposing group data.

If average score rises after training, do not stop there. Check completion rate, average time, and unanswered questions. Sometimes a higher score simply means weaker participants never reached submit. Sometimes time drops not because the material became clearer, but because the questions became too easy. Reporting And Analysis helps you spot the signal, but management decisions still require looking at several metrics together.

Marketing quiz and lead generation

For a lead-generation quiz, the key issue is not only score, but movement through the funnel: how many users started, how many reached submit, which answers indicate interest, how many contact fields were completed, and which result pages perform better. Reporting And Analysis shows submissions, charts and trends, while traffic-source analysis is usually better handled through Google Analytics Tracking or another site analytics tool.

Inside the reporting add-on, create a report for the specific quiz and the campaign period. Review submissions, completion, average time, and response distribution for questions that segment the audience. If a chart appears on the result page, it should help the user understand their own outcome, not expose your internal marketing segmentation. For example, it is safer to show "which type of solution fits you best" than to display aggregate answer statistics across all leads.

If submissions are high but lead quality is low, the problem may be in the questions, the result page, the promise in the quiz headline, or the traffic source. QSM Reporting And Analysis will show where users answer and complete the form, but it will not replace CRM validation or email follow-up analysis. In this use case, do not overload the result page with charts: the visitor came for a quick answer, not for an instructional report.

Customer feedback and event feedback

For feedback surveys, score is often irrelevant. The main questions are: which responses are selected most often, where users leave questions unanswered, how ratings change after an event or release, and whether there are differences between user groups. If the survey does not grade correctness, disabled score/points metrics are normal behavior, not an error.

In a custom report, choose the survey, the period, and responses. If questions are grouped into categories, use category filters for individual blocks such as product, support, content, event organization, or site usability. For open-ended answers, Reporting And Analysis may not be enough on its own, because text responses often require manual review or export. In that case, use the report to identify the problem area, then use Export Results for detailed record-by-record reading.

On the result page for a feedback survey, charts are often unnecessary. The user has already completed the action, and a thank-you message or next step is usually more valuable. A result page chart makes sense only when it genuinely helps the participant compare their response to the broader picture or understand their segment more transparently.

A Working Routine: How to Build Analytics Into Site Operations

Even a good report loses value if people open it randomly. With QSM Reporting And Analysis, it is better to define a working routine right away: when the dashboard should be reviewed, who checks reports, which changes are documented, how the result page is validated after updates, and who is responsible for data quality. This matters most on sites where quizzes affect learning, certification, internal evaluation, or commercial decisions.

After installation

Right after installation, do not create a dozen reports. One working scenario is enough:

1. One test quiz or survey.
2. One fresh submission.
3. One saved report with a clear name.
4. One chart that answers a real question.
5. One validation of a result page variable, if a public chart is actually needed.

This gives you a baseline. If something breaks later after a theme update, cache change, QSM core update, or add-on update, you will have a clear reference point: the test submission used to appear in Results, the report could see it via Date Range, the chart rendered, and the result page displayed the variable as a chart.

After changing a quiz or survey

Every change to the questions changes the meaning of the report. If you add a question, remove a category, change points, or rewrite result conditions, an old report may still open, but the period comparison becomes methodologically weak. In project notes or a working log, it is worth documenting what changed: question structure, score, categories, labels, result page variables, required contact fields, or page placement.

After the change, create a test submission with known answers. Check the raw result, the dashboard, the custom report, and the result page. If you use Compare, do not compare the pre-change period with the post-change period without adding context. Otherwise, you may draw the false conclusion that users are performing better or worse when in fact you changed the assessment tool itself.

After updating QSM core or the add-on

After updates, validate three surfaces: core quiz submission, the admin report, and the public result page. The QSM core and Reporting And Analysis changelogs include changes to rendering, database structure, dashboard UI, validation, security checks and result handling. Most updates are necessary and helpful, but any reporting layer should still be validated with a test pass after an update.

The minimum check is this: complete the quiz, confirm that the record appears in QSM - Results, open the report for the current date range, verify the chart, and if template variables are used, open the result page. If all of that matches expectations, the update can be considered stable. If not, check migration status, add-on activation, cache, the browser console, and any theme conflict first.

Access rules for the team

Teams often want to give report access to an instructional designer, marketer, or HR manager. Do that carefully. QSM Results may contain contact information, email, phone, user id, IP address, and other data. Even if the report itself shows aggregates, someone with QSM access may still be able to open details or export data through a related tool.

A good access model looks like this: the administrator is responsible for installation, updates, and security; the instructional designer or analyst gets only the level of access needed to read reports; the public result page shows only data that is useful to the participant; and CSV/PDF export is handled by someone who understands the site's data retention policy. If WordPress roles do not provide the needed granularity, it is better to restrict access and share the final report manually than to expose unnecessary personal results.

How to Improve a Quiz Based on the Reports

Reporting And Analysis becomes especially valuable when a report leads directly to action. That action may be small: rewrite one question, split a category, add clarification to the result page, reduce required fields, check mobile behavior, update a lesson before a weak topic, or create a separate report for a new user group. If nothing changes after reviewing charts, analytics turns into a ritual.

If one category is underperforming

Open the category report and look not only at average score, but also at individual results. If mistakes are spread across all questions in the category, the problem may be the learning material. If the mistakes cluster around one question, review the wording, answer options, points, and the correct answer. If unanswered questions are high, the item may be too long, unclear, or displayed poorly.

After changing the question, do not delete the old report. Create a duplicate, change the date range to the post-edit period, and compare the new structure on its own. That way, you do not mix the old and new methods. If you want to preserve the history, document in project notes that the category was changed.

If completion is dropping

Completion rate tells you whether the user reached the end, but not why. Check average time, unanswered questions, required contact fields, the number of pages, the submit button, mobile width, and possible JavaScript errors. QSM support forums include issues around the submit button, result page, and email flow, so troubleshooting should begin with completing the form as a regular user.

If the drop began after adding a result page chart, temporarily remove the chart variable and test again. If submit stopped working after a theme or cache change, investigate a conflict. If completion drops only on long assessments, break the questions into clearer pages or rethink the required fields.

If submissions are growing but decision quality is not improving

More submissions are only useful when the data leads to action. For a marketing quiz, compare responses with lead quality in your CRM or email platform. For a course quiz, review categories and repeat attempts. For a feedback survey, look not only at the number of responses, but also at the distribution of problematic options. Reporting And Analysis will point you in the right direction, but final decisions often require combining it with external data.

This is where the neighboring add-ons become especially useful. Google Analytics Tracking helps connect submit events to traffic sources. Export Results helps you export specific answers and contact fields. Advanced Assessment helps turn answers into labels and profiles. Reporting And Analysis remains the central screen for reading patterns inside QSM.

Video Walkthrough for Reporting And Analysis

The official product page includes a link to the video "Watch Reporting & Analysis Addon in Action," and the documentation embeds a video on analyzing quiz results in QSM. It is most useful to watch after you have gone through the text setup, because it helps you match section names, dashboard behavior, and the practical order of actions in the interface. It is especially useful for the intent "how to use QSM Reporting And Analysis," because it shows the product as a working screen rather than a feature list.

When watching, focus less on the general marketing message and more on the sequence: where the add-on opens, which dashboard blocks are available, how filters are selected, where charts appear, and what the final analytics view looks like. If your interface looks noticeably different, check your QSM core version, add-on version, database migration status, and the documentation for the new dashboard.

When QSM Reporting And Analysis Is the Right Choice

QSM Reporting And Analysis is worth using if you already have working QSM quizzes or surveys, data is collected regularly, and decisions need to be based on an aggregated view. The add-on is especially useful for educational tests, certification, employee training, customer feedback, event feedback, market research, and lead-generation quizzes where individual submissions matter, but patterns over time matter just as much.

Before rolling it out, verify the core results, complete the QSM migration if needed, review categories, points, result page templates, and user roles. Then create one narrow custom report, run a test workflow, compare the dashboard with raw results, and only after that expand the reporting system. This order protects you from the most common mistake: building conclusions from a polished chart without validating the input data first.

In short: choose the add-on when you need saved reports, filters, period comparison, summary stats, charts, and a clear way to display charts on the result page. Do not expect it to magically identify weak questions without a sound method behind it. The best results come when QSM Reporting And Analysis is built into the process: hypothesis - report - chart - raw result validation - quiz or course update - validation again.