Analyse response pattern


Response pattern analysis is currently an α alpha feature. Have you got any suggestions for how we can improve the functionality? We are always looking for feedback, so feel free to get in touch!

You can run the Response pattern analysis from the tab on your Participants page to automatically group duplicate responses into categories, making it easier to review and decide which participants to participants to include or exclude from your analysis.

Analysing response pattern

How it works

The Response pattern analysis feature uses large language models to examine open-ended responses across your survey participants. It categorises duplicates into two types:

  • Innocuous duplicates
    Short, common responses like “No”, “Nothing to add”, or “None”. These typically indicate low engagement on a specific question but aren’t flagged as high-risk since they’re brief and contextually appropriate.
  • Suspicious duplicates
    Longer, detailed responses that are identical or near-identical across multiple distinct participants. These patterns suggest non-genuine responses and are flagged as potentially problematic.

The main table displays each flagged pattern with:

  • Pattern type (Innocuous or Suspicious) Question where the pattern was detected
  • Pattern text (the duplicated response)
  • Word count
  • Number of participants who gave this response
  • Actions to review, include, or exclude affected respondents

Click on the number of participants for a detailed view of each respondent who provided that duplicated response. You can review their individual response text, quality rating, and inclusion status, then exclude specific participants from your analysis if needed.

Detailed response analysis

When this feature is available

The Response pattern analysis tab is available when your experiment meets the following requirements:

  1. You have a Conjointly licence
  2. Your experiment has at least 10 completed responses
  3. Your experiment includes at least one of these question types:
  4. Your team has not disabled LLM features in team settings