Matrix, distribution, constant sum, and multi numeric questions handle grids, fixed totals, and multiple related numbers on one screen. They are common in product testing, budget allocation, and attribute batteries.
Standard Matrix (Matrix / Likert)#
A grid of rows and columns. Each row is a statement; each column is a scale point (for example, Strongly Disagree → Strongly Agree).
When to use it:
- Agreement or satisfaction grids covering multiple items at once.
- Attribute ratings across several products or features.
Tip: You can add images and formatted text to both rows and columns for richer visual grids — great for product or concept testing.
Logic support#
Matrix questions have dedicated condition operators (e.g., "any row equals", "row count >=") that let you build logic based on how respondents fill in the grid. You can also use matrix questions as a source for section loops (loop over rows or filtered subsets of rows) and carry forward (carry only rows that match specific criteria). See Logic, Flow & Conditions for details.
Distribution (Constant Sum)#
Respondents allocate a fixed total (points, percentage, budget) across several options.
When to use it:
- Budget allocation questions.
- Time or share-of-wallet questions.
- Any scenario where the total must add up to a specific number.
Respondents see the total they need to reach (for example, 100%), and analytics show the average allocation per option.
Constant Sum#
Respondents allocate numeric values across items that must add up to a target total (not necessarily 100%). Use this when you need counts, points, or dollars rather than percentages.
A plugin variant also exists with enhanced controls (sliders, steppers) for mobile-friendly allocation studies. See Display Blocks & Plugins.
Multi Numeric#
Multiple labeled numeric fields in one question — useful when you need several related numbers on the same screen (for example, units sold per product line).
Configuration tips#
- Label each field clearly in the properties panel.
- Use validation rules where min/max per field matters for data quality.
Related guides#
- Question Types — overview and when-to-use table
- Logic, Flow & Conditions — matrix operators, section loops, carry forward
- Platform Feature List — plugin constant-sum UI and matrix-based plugins
Was this page helpful?