Entries stay in this page only. There is no submission, autosave or tracking script. Print to keep a copy; reloading or closing may lose your work. Use aggregate notes, not customer details, passwords or private access links.
1. Can a suitable buyer complete the buying path?
A ready provider status is setup evidence, not proof of a completed payment. A simulated buyer test makes no real payment. A delivery response or download prompt does not establish that the file opened; provider acceptance does not establish inbox arrival. Record those checks separately.
Record the product, edition, mode and exact dates shown by each report. A blank or unavailable measurement is not a verified zero. Keep QA, free claims and sandbox activity out of real paid-sales counts.
Do not divide these three counts blindly. Different date bases, cutoffs, channels and editions do not form one matched funnel. Use a specifically matched, mature cohort if a report provides one. A paid-date total is not necessarily retained revenue. An incomplete checkout alone does not prove a payment error.
Choose the issue supported by the current evidence. If the evidence is missing, make the next step a check rather than a claim that your product, copy or price failed.
If using Genesize “Track this improvement”: tracking a saved draft does not publish it. Its actual matching publication anchors equal seven-day edition windows; allow 24 more hours for checkout outcomes. These are checkout-created cohorts with payment within 24 hours, not the paid-date sales total on page 2. Earlier availability before publication observations began is unknown and cannot be backfilled. Short coverage, unrelated changes or unpublishing can prevent a valid comparison. Sparse activity cannot establish a winner. These dates are unrelated to a Search Console reporting baseline.