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

Integrations

Revenue signals

Outcome measurement is planned and not built. What it will require, and why no uplift claim is made today.

Planned2 min readReviewed 2026-09-21Markdown

On this page

  • What it would take
  • Attribution levels
  • What this rules out today
  • Stripe

Not implemented. No revenue data is collected, and no revenue outcome is measured or displayed anywhere in the product.

This matters more than an ordinary missing feature, because it is the difference between "this price is defensible" and "this price worked". Paywall Parity can currently make the first claim and not the second.

What it would take

Contracts and integrity first. A provider-neutral RevenueSignalProvider, with immutable, idempotent, normalized events carrying provider provenance, product identity, market, currency, event and effective times, deduplication keys, and reconciliation status. Without that, every number downstream inherits an unknown error.

Observed performance. RevenueCat for cross-store subscription context, Google Play for store-native reconciliation. Proceeds, payers, trials, conversions, renewals, cancellations, refunds — with explicit coverage reporting by product and market, so a gap in the data is visible rather than averaged away.

Deployment-linked impact. Each pricing deployment attached to before and after windows, controlled for seasonality, app releases, acquisition changes, promotions, and tax or FX movement. Forecast versus observed, with confidence ranges.

Attribution levels

Evidence would be labelled by how it was obtained, never presented as uniform:

LevelWhat it is
DirectionalSimple before-and-after observation. The weakest form.
ComparativeMatched market or product trend, with confounders annotated.
ExperimentalHoldout or staggered rollout with sufficient sample.

Directional evidence will never be described as revenue caused by Paywall Parity. Pre/post movement in a market where you also shipped a new onboarding flow tells you very little, and presenting it as attribution would be the central dishonesty of this product category.

What this rules out today

No uplift percentage. No ROI figure. No payback period. No "customers see X% more revenue". None of those can be computed, so none of them appear.

Stripe

Stripe is a possible later adapter for web or off-store payments. It is not a substitute for Play billing data and would not be presented as one.

PreviousApple App StoreNextCredential custody

On this page

  • What it would take
  • Attribution levels
  • What this rules out today
  • Stripe