When an AB test shows an amazing result, assume a bug first: verify tracking, the feature, and the experiment setup before celebrating (Twyman's Law). And always define triggering, evaluate only the users who could actually see the change. Including unaffected visitors dilutes the effect, drags out runtime, and can make a real win look like noise.

Context: Web (dev.to, 5 most common AB testing mistakes): describes two classic traps. Twyman's Law: any figure that looks interesting or different is usually wrong, so an amazing early result usually means a bug in the feature, the tracking, or the experiment design, and you must double-check before presenting it. No triggering: if a feature only affects registered users but you evaluate all visitors including anonymous ones, the dilution kills sensitivity and can make the test impossible to evaluate.