value-integritylisted

# Value integrity Counts reconcile, revenue does not. This is the most common state of a conversion setup that everyone believes is working, and it is the state in which return-on-spend figures get published. ## Find the shape of the error first Before theorising, pull the distribution of the value parameter as the platform received it, and the same distribution from the ledger. The shape names the bug. | What you see | What it usually is | |---|---| | One distinct value across every event | A hardcoded amount on the page | | A handful of values, wrong proportions | One template serving several prices, reading the wrong variable | | Right values, wrong total | Currency missing or mismatched, so the platform converted at its own rate | | Correct at first, drifting up over time | Refunds and cancellations never sent back | | Roughly a clean multiple of the ledger | Duplication, not a value bug. See `dedup-verification` | A single distinct value is the one to check first. It is common, it is invisible in every dashboard, and it usually arrives as a placeholder someone meant to replace. ## Decisions you have to make once and hold These are not bugs, but disagreeing about them produces the same symptom. - **Gross or net.** Does value include tax, shipping, discounts? Choose, write it down, and make the ledger comparison use the same definition. - **Trial then charge.** Sending the full subscription value at trial start overstates revenue by the entire trial-to-paid fai