Data Point Weights
Not all data points are created equal. A missing DKIM configuration is more impactful than an inconsistent naming pattern on a handful of lists. JetStack AI’s weighting system ensures that the most important data points carry proportionally more influence over your audit scores.
This page explains exactly how weights are calculated.
Weight Formula
Section titled “Weight Formula”Every data point’s weight is calculated as:
Weight = Base Weight x Fundamental Multiplier x Severity Multiplier
Each component is determined by the data point’s metadata.
Base Weight from Priority
Section titled “Base Weight from Priority”Every data point has a priority level from P1 (most critical) to P4 (least critical). The base weight maps directly from priority:
| Priority | Base Weight | Description |
|---|---|---|
| P1 | 4 | Mission-critical items that directly affect portal functionality or data integrity |
| P2 | 3 | Important best practices that significantly impact efficiency or accuracy |
| P3 | 2 | Recommended practices that improve quality and maintainability |
| P4 | 1 | Nice-to-have optimizations and minor improvements |
A P1 data point starts with 4x the influence of a P4 data point before any multipliers are applied.
Fundamental Multiplier
Section titled “Fundamental Multiplier”Some data points are marked as fundamental — they represent foundational requirements that everything else depends on. Examples include having DKIM/SPF configured for email sending, or having at least one active pipeline for sales tracking.
| Fundamental | Multiplier |
|---|---|
| Yes | 1.5x |
| No | 1.0x (no change) |
Fundamental data points receive a 50% weight boost because their absence undermines the value of many other features.
Severity Multiplier
Section titled “Severity Multiplier”Data points with critical severity get an additional multiplier. Critical severity means the finding, if poor, represents a serious risk to deliverability, data integrity, compliance, or revenue tracking.
| Severity | Multiplier |
|---|---|
| Critical | 1.3x |
| Non-critical | 1.0x (no change) |
Combined Examples
Section titled “Combined Examples”Here is how the formula plays out for different combinations:
| Priority | Fundamental | Critical | Calculation | Final Weight |
|---|---|---|---|---|
| P1 | Yes | Yes | 4 x 1.5 x 1.3 | 7.8 |
| P1 | Yes | No | 4 x 1.5 x 1.0 | 6.0 |
| P1 | No | Yes | 4 x 1.0 x 1.3 | 5.2 |
| P1 | No | No | 4 x 1.0 x 1.0 | 4.0 |
| P2 | Yes | Yes | 3 x 1.5 x 1.3 | 5.85 |
| P2 | No | No | 3 x 1.0 x 1.0 | 3.0 |
| P3 | No | No | 2 x 1.0 x 1.0 | 2.0 |
| P4 | No | No | 1 x 1.0 x 1.0 | 1.0 |
The highest possible weight is 7.8 (P1 + fundamental + critical). The lowest is 1.0 (P4, not fundamental, not critical). That means the most important data points carry nearly 8x more influence than the least important ones.
How Weights Affect Block Scores
Section titled “How Weights Affect Block Scores”Weights feed into the block scoring formula:
Block Score = Sum(dataPointScore x weight) / Sum(weights)
This means a single P1 fundamental critical data point scoring 0 will drag a block score down far more than a P4 data point scoring 0. Conversely, fixing that high-weight data point produces the biggest score improvement.
Practical Impact
Section titled “Practical Impact”When reviewing audit results, pay attention to the weight of each finding. A data point with a weight of 7.8 scoring at 30 has far more impact on your overall score than a weight-1 data point scoring at 30.
This is why the Recommendations system prioritizes fixes based on weight — addressing high-weight data points first produces the fastest score improvement.
Where to See Weights
Section titled “Where to See Weights”In the audit results view, each data point displays its priority level (P1-P4) and any fundamental or critical badges. While the exact numeric weight is not shown in the UI, you can calculate it using the formula above: multiply the base weight by the applicable multipliers.
The scoring breakdown at the block and section level shows how individual data points contribute to the aggregate, making it clear which items are pulling your score up or down the most.