Understanding Quantity, Sum, and Parameter Metrics

Prev Next

Introduction

In Mapp Intelligence, custom parameters automatically generate additional metrics based on the selected datatype and aggregation. In analyses, this can produce metric pairs that look similar but represent different calculations.

For example:

  • Qty Internal Search Results

  • Internal Search Results

These are not duplicates. Each serves a different analytical purpose.

Note

This article describes metrics generated for custom parameters in Mapp Intelligence. Predefined system metrics may follow different naming conventions and do not necessarily use the Qty prefix.


How datatype and aggregation interact

The datatype of a custom parameter determines which aggregation options are available:

  • Text parameters always use Quantity.

  • Generic parameters always use Quantity.

  • Figure parameters support Quantity and additional aggregations such as Sum.

Every parameter type produces a Quantity metric. Figure parameters can additionally produce metrics based on the submitted values.

The following sections use one custom parameter to illustrate this behavior: Internal Search Results. The parameter stores the number of results returned after a user performs an internal search. Two events are tracked: one search returns 5 results, another returns 3.


The Quantity metric

Quantity measures how often a parameter was tracked. The generated metric name follows this pattern: Qty [Parameter Name].

Applied to the example:

Metric

Value

Meaning

Qty Internal Search Results

2

Two searches were tracked

The submitted values (5 and 3) are not part of this calculation. Quantity counts occurrences only.

Use Quantity to:

  • Verify that data is being collected.

  • Measure how often an event occurred.

  • Build formulas such as averages.

On its own, Quantity often gains analytical value only when combined with other metrics.


Quantity and Sum

For Figure parameters, the Quantity and Sum aggregation generates two metrics:

  • Qty [Parameter Name]

  • [Parameter Name]

Applied to the example:

Metric

Value

Meaning

Qty Internal Search Results

2

Number of tracked searches

Internal Search Results

8

Total of submitted search results

A Sum metric viewed in isolation often lacks context. A total of 100 search results could mean 10 searches with 10 results each, 5 searches with 20 results each, or 100 searches with a single result each. The total alone does not explain the underlying distribution.

Combining both metrics enables meaningful calculations. For example, the average number of results per search: Internal Search Results ÷ Qty Internal Search Results = 8 ÷ 2 = 4.

On average, each tracked search returned four results.


How parameter names affect generated metrics

Metric names are generated automatically from the parameter name and the selected aggregation. The system prepends Qty for Quantity metrics: Qty [Parameter Name].

The system does not check whether the parameter name already contains terms such as Quantity, Qty, Count, or Sum. The prefix is always added.

Example with a redundant parameter name:

Parameter name

Generated metrics

Quantity Search Results

Qty Quantity Search Results
Quantity Search Results

This behavior is expected but can make analyses harder to read.

Best Practices

  • Avoid terms such as Quantity, Qty, Count, or Sum in parameter names.

  • Use names that describe the tracked information.

  • Consider how generated metric names will appear in analyses.


Common misconceptions

Misconception

Reality

Qty reflects the submitted value.

No. Qty counts occurrences only.

Qty and the parameter metric contain the same information.

No. They represent different calculations.

The Sum metric always provides the final analysis result.

Not always. Meaningful results often come from combining multiple metrics.

Text and Generic parameters can create Sum metrics.

No. Text and Generic parameters only produce Quantity metrics.


How to set up custom parameters