Skip to content

Experiment recipes

Copy-paste starting points for common research designs. Adjust page counts and group names to match your study.


Goal: Everyone sees the same flow.

  • No randomisation on sections and pages
  • Optional display logic for screener skip or answer-based follow-ups

Goal: Reduce order bias without hiding content.

  • Randomise order at page level (blocks) or section level (pages)
  • Keep instructions on a separate page with no randomisation

Goal: Each person sees some modules, not all; group names not needed in results.

  • Split modules into a section
  • Present a subset → e.g. 2 of 5 subsections
  • Do not enable Randomisation groups

Classic A/B test (one variant per participant)

Section titled “Classic A/B test (one variant per participant)”

Goal: Group A vs Group B with named conditions in results.

  1. Create a section with one page (or subsection) per variant
  2. Present a subset → 1 of N
  3. Enable Randomisation groups → map Group A/B to each target
  4. Add shared post-task questions outside the randomised section
  5. Keep thank you page outside the section

Goal: Three or more between-subjects arms with balanced assignment.

  • Same as A/B with N pages and N groups (or N blocks on one page)
  • Use weighted randomisation if groups are not equal size
  • Test every arm in preview with Follow logic

Goal: Same task (or parallel tasks), different prototypes per group — including multi-page flows with per-page starts and shared or per-task ends.

  1. Add prototypes and assign a source prototype on task pages in Build
  2. Configure interactive tasks (start, end, paths) on those pages
  3. Compare assets at section level when multiple pages share one source asset, or page level for a single task screen
  4. Map variant task mapping (start / end / success) on each non-original prototype — use Per page or Per task when source pages or goal tasks differ
  5. Optionally combine with section randomisation if each group also has a different task flow
  6. Define groups in the creation wizard or inline in compare assets

Example: Page 4 (goal-based, start + end) and Page 5 (first click, start only), two age cohorts, two prototype files — see Multi-page flow use case in Compare assets.


Goal: Condition comes from the URL, not random assignment.

  1. Create a URL parameter variable (e.g. ?condition=B)
  2. Display logic on each page or section: show when variable equals the right value
  3. Do not use section subset mode — assignment comes from the link

Mixed: random group + conditional follow-up

Section titled “Mixed: random group + conditional follow-up”

Goal: Between-subjects main task, then answer-driven paths.

  1. Randomisation groups for the main between-subjects block
  2. Shared later pages with display logic based on answers
  3. Branching to jump qualified participants to the main block