CRO Glossary
Experiment Metadata
The structured record of who, what, when, and how for a test — hypothesis, owner, dates, variants, and metrics used to track and audit it.
Experiment metadata is the set of structured details attached to every test that let a team find, understand, and audit it later without re-reading the full experiment design document. Typical fields include the hypothesis, start and end dates, primary and guardrail metrics, traffic allocation, owner, targeted audience or page, and status (running, stopped, shipped, archived).
This matters because experimentation programs scale fast, and without consistent metadata, institutional knowledge disappears the moment the person who ran a test moves teams. Good metadata turns a pile of past tests into a searchable knowledge base — you can answer questions like "have we ever tested pricing page layout?" or "what was the guardrail metric on that checkout redesign?" in seconds instead of digging through Slack history.
For example, a well-tagged experiment record might read: hypothesis — "reducing form fields from 8 to 4 will increase signup conversion without hurting lead quality"; owner — growth team; dates — March 3–17; primary metric — signup conversion rate; guardrail — lead qualification rate; result — +6.2% lift, shipped.
Teams that skip metadata discipline often end up re-running tests they've already tried, because nobody can reconstruct what was tested, on whom, or why it did or didn't ship. Tools like ABWatcher exist partly to enforce this structure automatically rather than relying on tribal memory.
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 experiment metadata.
Live A/B tests at 1,000+ high-converting brands, with plain-English hypothesis and takeaway.