Configure How to Treat Missing Values
In general, there are many ways to handle missing values. For example, you can discard them, replace them with a specific value, or impute them based on values of other similar users. The best approach generally depends on what you want to measure. For example, if you measure latency, it’s sensible to just discard the users with missing values. If you measure the minutes of music played, then users with missing values have played zero minutes of music. Confidence allows you to configure how to handle missing values for users, or entities, more generally. By default, Confidence replaces missing values with zero if you are using theSUM,
COUNT or COUNT_DISTINCT aggregations. For other aggregations, Confidence discards users with
missing values by default. You can override this behavior in the Missing Values section of a
metric, see below.

Discarding users with missing values can lead to sample ratio mismatch for a specific metric.
For example, if the treatment increases the chance that a user visits a particular part of the
app that you want to measure, then the treatment group has fewer users with missing
values than the control group. Because of the sample ratio mismatch, the two
groups might no longer be comparable. In this situation, a bias in which users are included in each group’s
metric value can drive the significant differences you detect.
IFNULL(measurement, 1) instead of just
passing measurement to Confidence.

