All terms

CRO Glossary

Clickjacking (in Testing Context)

A UI bug where a test variant's layout shift causes users to click the wrong element, inflating or deflating metrics.

In the context of experimentation, clickjacking refers to unintended layout or timing issues in a test variant that cause users to click on something other than what they meant to, producing misleading interaction data. This is distinct from the security exploit of the same name; here it's an accidental artifact of implementation rather than malicious intent, but the effect on your metrics is just as real.

It typically happens when a variant loads asynchronously, shifts content after the page has rendered, or overlaps a button with another clickable element for a split second. Users who intended to tap one thing end up tapping another, and the resulting click-through or conversion numbers for that variant become unreliable, often inflated for whatever element happened to end up under the user's finger.

A common example: a test variant adds a promotional banner above the fold that loads a beat later than the rest of the page. Users trying to tap a product link instead tap the banner as it slides into place, producing an artificially high click rate on the banner and an artificially low one on the product link. The result looks like a clear winner until someone checks session recordings and realizes it's a layout timing bug, not genuine user interest.

Practitioners catch this by reviewing session replays or heatmaps for variants with suspiciously large effect sizes, checking for cumulative layout shift in variant code, and treating any metric swing that can't survive a qualitative sanity check with skepticism. It's a reminder that instrumentation problems can masquerade as real lift.

Related terms

See this in the wild

ABWatcher watches how top teams apply clickjacking (in testing context).

Live A/B tests at 1,000+ high-converting brands, with plain-English hypothesis and takeaway.