Paywall Parity/Guidelines
Run a free audit

Start here

  • Overview
  • Quickstart
  • Safety model

Concepts

  • Store baselines
  • Parity targets
  • Strategies
  • Confidence
  • Drift
  • Protected markets

Workflows

  • Connect a store
  • Review recommendations
  • Stage and publish

Reference

  • Formulas
  • Error codes

Integrations

  • Google Play
  • Apple App Store
  • Revenue signals

Trust and operations

  • Credential custody
  • Methodology

Concepts

Confidence

How the confidence score is computed, the thresholds that gate a recommendation, and when the system abstains entirely.

Shipped3 min readReviewed 2026-09-21Markdown

On this page

  • The bands
  • How the score is computed
  • The 5% floor
  • What makes a recommendation approvable
  • What is not implemented

Confidence is a decision control, not a badge. It determines whether a recommendation can be acted on at all.

The principle: weak evidence should produce a request for better data, not a confident-looking guess.

The bands

ScoreLevelDecision
below 0.40Very LowAbstain
0.40 – 0.59LowAbstain
0.60 – 0.74MediumProvisional
0.75 – 0.89HighNormal
0.90 and aboveVery HighNormal

Abstain means no change is recommended. The screen shows what evidence is missing instead of a number you should not trust.

Provisional means the recommendation is shown, identified as provisional, and requires explicit acknowledgement. The intent is a smaller staged change rather than the full move.

Normal means it can proceed through ordinary review.

How the score is computed

Five weighted components, each between 0 and 1:

ComponentWeightWhat it measures
Data coverage0.35How many of the three economic inputs are present (PPP, price level, income).
Freshness0.20How recent the economic observations are.
Store support0.20Whether the store actually supports pricing in this market.
Rounding rule0.10Whether a rounding increment is known for the market's currency.
Stability0.15How far the adjusted factor sits from 1.0 — a large move is a less certain one.

The result is rounded to two decimal places.

Data coverage carries the most weight because it is the component most often at fault. A market with only PPP and no income or price-level data scores 1/3 on coverage, which alone costs it 0.23 of the total.

The 5% floor

Separately from confidence, a recommendation whose change is smaller than 5% is not surfaced. Below that threshold the change is within the noise of rounding and exchange-rate movement, and acting on it costs more attention than it returns.

This is why a market can show a different parity target in the matrix without generating a recommendation.

What makes a recommendation approvable

All four must hold:

  • status is open;
  • the product has not been withdrawn from the store;
  • the confidence decision is not abstain;
  • the absolute change is at least 5%.

The interface checks these before enabling the button, and the server enforces them again on submission. Approving a batch reports each skipped item individually with its reason — a reviewer who selected forty needs to know which ones did not go through.

What is not implemented

Three parts of the confidence design are specified but not built:

  • Visible components. Today the score is shown; its five parts are not broken out on screen.
  • Higher thresholds for protected or high-revenue markets. The bands are currently global.
  • Calibration against observed outcomes. The score has never been checked against what actually happened after a price change, because outcome measurement is not built. Treat it as a measure of evidence quality, not of predicted success.
PreviousStrategiesNextDrift

On this page

  • The bands
  • How the score is computed
  • The 5% floor
  • What makes a recommendation approvable
  • What is not implemented