Couple of options jump to mind @Zeus Collected. I’ll assume you’re passing an event along the lines of ‘survey answered’ (or whatever you call it) when the user submits their answer.

Option 1 - Use an object array passed with ‘survey answered’ then split it in Amplitude Data

For example…

'answers':>
   {
      'A': 'yes',
      'B': 'no',
      'C': 'yes',

      ...

      'N': 'no'

   }
]

...yes/ no representing whether the given checkbox was selected. You’ll have ‘answers’ as an event property in Amplitude then, but given it’s an object array you can split it in Amplitude data (https://help.amplitude.com/hc/en-us/articles/9623000954907-Cart-analysis-Use-object-arrays-to-drive-behavioral-insights#h_01GGX3KMYSJX6EBW6WHRC7PEMH) which would yield a further N event properties (one for each answer option). If you’ve got more than one question passed in a single ‘survey answered’ event you can still use this; each element of the array then passes answers for each individual question, and you can add a variable where the value identifies the question (‘question’: ‘question 1’, ‘question’: ‘question 2’, etc).

Option 2 - Use a single string and split that

For example, you could pass this event property (I’ve gone with a pipe delimiter, but that’s up to you)…

'answers': 'A_yes|B_no|C_yes|...|N_no'

Then create a Derived Property (https://help.amplitude.com/hc/en-us/articles/5874857623707-Derived-properties), say ‘answers (split)’, in Amplitude data….like this (but obviously with your ‘answers’ event property!).

Again this can be modified if you’ve more than one question in the event, for example…

'answers': 'q1_A_yes|q1_B_no|C_yes|...|qN_N_no'

Which one to use? Up to you really….could be argued that Option 1 is more straightforward for engineers to set up in your website/ application (?!) , while Option 2 only uses 2 event properties rather than N+1 and is arguably more user friendly for your end users in Amplitude as the distribution chart is then pretty simple. I’d personally go Option 2, but as I say, it could be different for you. There could also be other solutions too, these are just the 2 that came to mind immediately.

Hope that helps!

It was even easier than I was expecting… we tried passing all selected values in an array property and this works perfectly.

Ex.: user selects A,D,F options. We pass the event with the property tA,D,F].

The segmentation chart automatically shows the distribution of options.

User segmentation can use a specific value of the array.

So basically, everything was supported by Amplitude without custom/derived event/properties.

Thanks !