Skip to main content

Statistics

Statistics helps you calculate summary metrics and understand numeric values in a dataset.

Use Statistics when the main task is to summarize, compare, or inspect numeric Fields rather than change Record-level data. It helps turn raw Fields into counts, totals, averages, ranges, and other reviewable measures.

What Statistics is for​

Statistics is a good fit when you need to:

  • calculate totals, counts, averages, minimums, or maximums
  • summarize numeric Fields by group or category
  • compare values across periods, regions, owners, or statuses
  • inspect distributions and identify unusual values
  • create a reviewable summary before or after another WebHammers step

What a Statistics configuration does​

A Statistics configuration defines which values should be summarized and how.

A strong configuration usually includes:

  • the input dataset
  • the numeric Fields to analyze
  • any grouping Fields
  • the summary measures to calculate
  • filters or scope rules, if needed
  • a review plan for outliers or unexpected results

Why teams use Statistics​

Teams often need a quick, repeatable way to understand the shape of a dataset.

Statistics can help confirm that a File is reasonable before downstream use, compare outputs after processing, or provide summary evidence for a review, reconciliation, or operational check.

Typical Statistics workflow​

A common workflow looks like this:

  1. identify the dataset and numeric fields to summarize
  2. decide whether results should be grouped
  3. create or select a Statistics configuration
  4. test on a representative sample
  5. run the configuration on the intended input
  6. review metrics, outliers, and surprising values
  7. save or share the summary as needed

What makes a Statistics setup effective​

The best Statistics configurations are tied to a clear question.

A strong setup usually has:

  • a specific business purpose
  • the right numeric fields
  • meaningful grouping Fields
  • summary measures that answer the question
  • a way to review unexpected values

When Statistics is not the best starting point​

Statistics is not usually the first Tool to use when:

  • source values need to be cleaned before numbers are ready to summarize
  • duplicate records need to be resolved before totals will be accurate
  • Records need to be filtered, split, or joined first
  • the main task is record-level validation or correction

In those cases, prepare the data first, then use Statistics when the values are ready to summarize.

Continue with these pages:

  • When to use Statistics
  • Create a Statistics configuration
  • Run Statistics
  • Statistics examples
  • Statistics FAQ