Skip to content
~/reflective_data

analytics-dictionary / term / experimentation

Server-side testing

Server-side testing runs experiments in your backend, so users get the assigned variant before the page is rendered.

Written by Reflective Data experts · updated Oct 5, 2026

Because the decision happens on the server, there is no flicker and you can test anything: pricing, search ranking, emails or APIs. It requires engineering involvement and an SDK.

It suits product and complex logic tests; client-side tools suit quick visual changes.

related

Client-side testingFeature flagFlash of original content (FOOC)

// how we can help

We set up, audit and run experimentation programs on any tool. A/B testing services → · Audits

more in experimentation

adobe-target.md

Adobe Target

Adobe Target is Adobe testing and personalisation tool, part of Adobe Experience Cloud.
sample-ratio-mismatch.md

Sample ratio mismatch (SRM)

A sample ratio mismatch is when the actual split of users between variants differs from the…
randomization-unit.md

Randomization unit

The randomization unit is what gets assigned to a variant: a user, a session, an account…
type-1-and-type-2-errors.md

Type I and type II errors

A type I error is a false positive, declaring an effect that is not real; a…
launchdarkly.md

LaunchDarkly

LaunchDarkly is a feature management platform used to control feature rollouts with flags.
one-tailed-vs-two-tailed-test.md

One-tailed vs two-tailed test

A one-tailed test looks for an effect in one direction only; a two-tailed test looks for…

← full analytics dictionary