Match Type — Numeric Range

Match Type — Numeric Range

Numeric Range is a comparison method designed for number fields. Instead of requiring an exact match, it allows values to differ by a configurable amount and still be considered a match.

A match criterion row with Numeric Range selected as the match type, showing the Lower Limit and Upper Limit numeric inputs and the Use Percentage checkbox

How Numeric Range Works

Numeric Range compares two numeric values and checks whether the difference between them falls within your specified tolerance. If the difference is within bounds, the pair scores as a match for that criterion. If the difference exceeds the tolerance, the score is zero.

For example, with a tolerance of 2:

  • 30 vs 31 — difference is 1, within tolerance. Match.
  • 30 vs 32 — difference is 2, within tolerance. Match.
  • 30 vs 33 — difference is 3, exceeds tolerance. No match.

Configuring Tolerance

Two settings control the acceptable range:

  • Lower Limit — the maximum amount the target value can be below the source value
  • Upper Limit — the maximum amount the target value can be above the source value

Setting both limits to the same value creates a symmetric tolerance. You can also set asymmetric limits if needed — for example, allowing values to be up to 5 above but only 2 below.

Absolute vs. Percentage Tolerance

The Use Percentage checkbox switches the tolerance mode:

  • Unchecked (absolute) — the limits are fixed numbers. A Lower Limit of 2 means the value can be at most 2 units below.
  • Checked (percentage) — the limits are percentages of the source value. An Upper Limit of 10 means the target can be up to 10% higher than the source.

Tip

Use percentage mode when comparing values that span a wide range. For example, a fixed tolerance of 5 is meaningful for ages but insignificant for revenue figures in the millions. Percentage mode scales automatically.

Best Use Cases

Numeric Range is ideal for:

  • Ages — a person's age may differ by 1 between two records due to data collection timing
  • Amounts and quantities — order amounts that differ slightly due to rounding or adjustments
  • Measurements — height, weight, or other physical measurements with minor recording differences
  • Dates stored as numbers — year values or serial dates that should match within a range

When Not to Use Numeric Range

Do not use Numeric Range for fields that happen to contain numbers but should match exactly:

  • Phone numbers — these are identifiers, not quantities. Use https://help.matchlogic.io/article/257-match-type-exact-match or https://help.matchlogic.io/article/258-match-type-similar-text.
  • ZIP codes — numeric codes should match exactly.
  • Account numbers — any difference indicates a different account.

Important

If a field contains non-numeric values (letters, special characters), Numeric Range will not be able to compare them and the criterion will score 0 for those records. Ensure your data is clean before using this match type.