Skip to content

Compare assets

Compare assets (asset display logic) assigns which prototype a participant sees on a page or section in a usability test.

It does not control which pages appear — that is Section randomisation or Display logic.


FeatureControls
Section/page RandomiserWhich pages, subsections, or blocks appear
Compare assetsWhich prototype appears on a page that is already visible

They combine: a participant might be assigned to Group B (section randomisation), land on Page 2, and see Prototype B (compare assets).


DriverUse when
Randomisation variableRandom A/B prototype assignment with balanced groups
ConditionPrototype depends on URL, sample, answers, or another variable

Configure on a page or section that has prototypes attached. You can create a randomisation variable inline or reuse an existing one — the same pattern as Randomisation groups.


  1. Add prototypes in Assets & Media
  2. Assign a prototype to a page in Build
  3. Open Path Logic → Compare assets on that page or section
  4. Choose driver (randomisation or condition)
  5. Map each group value to a prototype
  6. Set fallback behaviour if no rule matches

Both can use randomisation variables with named groups, but they solve different problems:

Randomisation groupsCompare assets
ChangesWhich pages/blocks/subsections showWhich prototype shows
Study typesSurveys and usability testsUsability tests (prototype pages)
Typical useDifferent task flows or question setsSame task, different designs

You can use both in one study: randomisation groups pick the task path; compare assets picks the prototype on that path.


The usability test creation wizard Groups step can define groups upfront. These work with compare assets, randomisation variables, and display logic.

See Creating a usability test and Prototypes and assets.