CRO Glossary
Server-Side Testing
Running A/B tests by changing logic on the backend rather than in the browser, allowing deeper and more complex variants.
Server-side testing means the variant assignment and rendering logic happen on the application server or in a service layer, rather than being injected into the page client-side with JavaScript after it loads. This is the opposite of typical client-side visual editor tools, which swap DOM elements in the browser once the page has already rendered.
The main advantage is that server-side tests can touch things a client-side script can't easily reach: pricing logic, algorithm changes, backend recommendation engines, checkout flow restructuring, or anything requiring a database query. It also avoids the visible 'flicker' of content changing after page load, which can itself bias results by making users notice they're in an experiment.
The tradeoff is speed of implementation: server-side tests typically require engineering time to build and ship behind a feature flag, whereas a marketer can often launch a simple client-side test alone. Many mature CRO teams run quick copy and layout tests client-side but move anything structural, like a new checkout flow or pricing test, to server-side implementation to reduce flicker and enable more powerful variants.
Related terms
Shrinkage Estimator
A statistical adjustment that pulls noisy per-variant or per-segment estimates toward an overall average to reduce overfitting to randomness.
Flicker Test
A diagnostic check to confirm whether users briefly see the original page before a variant renders in client-side experiments.
Pre-Experiment Bucketing Audit
A review process confirming users are being randomly and evenly assigned to experiment variants before launch.
Above-Fold Exclusion Rule
A test-design rule that deliberately prevents changes to above-the-fold elements so an experiment isolates below-the-fold effects.
Flicker-Free Testing
A technical setup that prevents users from briefly seeing the original page before a test variant loads.
Orthogonal Test Design
A test structure where multiple variables are changed independently so their individual effects can be measured without interference.
See this in the wild
ABWatcher watches how top teams apply server-side testing.
Live A/B tests at 1,000+ high-converting brands, with plain-English hypothesis and takeaway.