project_
LaunchOS · Ton Luccas
each version tests one hypothesis and remains available for comparison. the system follows visitors through confirmed payment, showing which page produced real sales and what to test next.
view live siteinside the product_
how the system works
from what people experience to what keeps the product running
each version has its own address and remains accessible after the test. a record shows which version is live, which is newest, and which ones are locked.
browser and server share one conversion identifier, preventing duplicate events. a sale counts only after the payment provider confirms it.
the page reaches the browser ready to use. the server only handles the steps that require confirmation, so traffic spikes do not force it to rebuild the interface for every visit.
product in use_
project screens
why it was built this way_
important decisions
the choices that shaped the experience, operations, and product boundaries.
preserve each version tested
when a new page goes live, the previous version stays available at its own address. this preserves both the comparison and the experiment history.
do not count the same conversion twice
browser and server use the same identification to recognize the event. the campaign report receives a single conversion.
count confirmed sales, not clicks
a sale counts only when the payment provider confirms it, so advertising decisions are based on real revenue.
change one hypothesis at a time
each version changes one variable, making its effect measurable. once a test begins, that version remains unchanged.
see the other works
