What is the best way to capture multi select data in Adobe Analytics?

[SupunD]

I have a multi-select list where I am firing an event and a serialized event. 

Let's say that I have 4 items on this list. At the moment, the selected values are captured in an array in the Front-End. How can I translate this information into Adobe Analytics? Can I capture this information in the eVar? 

Thanks in advance! 

[Jennifer_Dungan]

Depending on the length of the potential values, you can use a "List Enabled" prop, to pass all the values with your selected delimiter.

For example:

s.propX = "value a,value b,value c,value d";

or

s.propX = "value b,value d";

If propX is set up as list enabled with comma as your delimiter, each value would be split to its own row in your report..

		Occurrences
PropX		6
	value b	2
	value d	2
	value a	1
	value c	1

Note that a prop enabled list can hold up to 100 characters maximum. So if the values you are passing will exceed that characters count, this is a bad choice to use.

The are also 3 list parameters available to you, these are basically like eVars, they can have an expiry assigned to them (default is Visit, but this can be changed for your needs). 

Like the list enabled prop, you can choose your delimiter, but unlike props, lists can take up to 255 characters per item... you can pass as many items as you need. 

The report would look similar to above (assuming you used Hit expiry if pairing with occurrences metric, but you could use ListX Instance to get when the values are set, with a longer Expiry like Visit you can correlate to actions later in the Visit).

[RobertBlakeley]

For multi-select we generally do not do the list variable approach, which is often a good approach for multiple values created with one action. My Business typically just wants to know which options are being used or which can be dropped because they are not used. How much a given option is being used as an indication of user intent is typically of less interest, mostly because of how we use multi-select in our designs.

Thus, using a list variable is a bit of an overkill for us. We pass the values with a delimiter into a regular variable. We can easily see what combinations of options are used and can use report filtering to see the use of any given option. If we need to get fancy, there is always Excel.

[avo22]

Do you pass the list items as "item1, item2, item3" or "[item1, item2, item3]"? I'm doing the latter, and I'm running into an issue where only the lists of length one are reported 

[RobertBlakeley]

value = objectsName_ item1-item2-item3

[Jennifer_Dungan]

So long as this doesn't hit the 255 character limit, this approach is fine

And yes, I get that the "related options" would be harder in the list solution, but if the values are long, or you have a lot of them, it's still a viable option.

Like most things in Analytics, there are many ways to do things... be creative!