The Revenue QA glossary.
Plain-English definitions of the terms behind ecommerce revenue leaks: the bugs, friction, and tracking gaps that cost sales between the click and the purchase.
Revenue QA
The practice of checking the parts of a site that directly affect revenue, the checkout, cart, product pages, forms, tracking, mobile flows, and paid landing pages, across the browsers and devices shoppers actually use. Traditional QA asks whether the site works. Revenue QA asks whether the buying path is costing you money.
Revenue leak
A bug, friction point, or tracking gap on the buying path that costs sales without showing up as a clear error. It looks like flat conversion, abandoned carts, lower ROAS, and traffic up but revenue flat.
Buying path (conversion path)
The sequence a shopper moves through from arrival to purchase: landing page, product page, add-to-cart, cart, checkout, payment, confirmation. Each step is a place revenue can leak.
In-app browser
The embedded browser inside apps like Instagram and TikTok. Pages often load slower or break there compared to Chrome or Safari, and a large share of paid social traffic lands in them, so problems here directly tax ad spend.
Add-to-cart failure
When the add-to-cart button does not respond or errors on a specific browser or device, so shoppers cannot buy even though the page looks fine. A classic example is an unresponsive button on Safari Mobile.
Tracking gap (pixel gap)
A missing, duplicated, or misfiring analytics or conversion event. It distorts the numbers you optimize from, so you may be making decisions on bad data without knowing it.
Dead CTA (rage tap)
An element that looks clickable but is not, or a button that does nothing. Shoppers tapping it repeatedly is a signal of friction or a bug on the page.
Cart drawer
The slide-out mini-cart that appears after add-to-cart. A common home for mobile-only bugs: it fails to open, shows the wrong total, or hides the checkout button.
Cross-browser issue
A problem that only appears on certain browsers or devices while desktop Chrome looks fine. Because most teams test on desktop Chrome, these are some of the most expensive and most missed leaks.
Checkout friction
Anything that slows or blocks checkout: shipping surprises, failed discount codes, slow steps, or form errors. It shows up as cart and checkout abandonment.
Core Web Vitals (revenue lens)
Google's page-experience metrics for load speed, interactivity, and visual stability. For an ecommerce store, slow or unstable pages cost conversions, not just rankings.
Audit before you test
The principle that a broken buying path makes an A/B test measure bugs instead of ideas. Fix the leaks first, then test the upside, so your results mean something.