listVars Implementation Workaround

[WillWa2]

Hi everyone,

Is there a workaround for configuring listVars because of a limited amount?

We are tracking a form where a user a provide multiple responses per question (i.e. select all that apply). These responses will be pushed to an array and assigned to a variable when the form is submitted.

In Adobe Launch, will be captured as a Data Element, then mapped as a eVar/prop. These will be mapped to a listVar, to help with our reporting measures. 

There are 5 of these questions we like to track using the above steps. However, we noticed that we are allotted only 3 listVars.

Did anyone ever come across such an issue before? If so, what steps were taken to achieve this.

Thanks!

-Will

[Harveer_SinghGi1 · Accepted solution]

Hi @WillWa2 ,

I'd suggest you use a single listVar which tracks the question-response pairs like below,
list1 = "que1|resp1,que1|resp2,que1|resp3,que2|resp1,que2|resp2,que2|resp3,que2|resp4"

In above example I'll enable listVar1 with comma (,) as delimiter and when this data is reported in AA I'll see list1 row items reported like below,

• que1|resp1
• que1|resp2
• que1|resp3
• que2|resp1
• que2|resp2
• que2|resp3
• que2|resp4

Then you can add classification on top of this list var to split these values on pipe (|) in two reports for question and response.

This way you'll have all the information related to all the questions and their related responses in a single variable.

Cheers!

[bjoern__koth]

Hi @WillWa2 

the limited number of listVars has always been been a problem.

Possible workarounds include

• tracking them together with another ever that gives context to them, as suggested here https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/possible-to-get-more-than...
• or alternatively using for instance a prefix in the individual values which would potentially give your more flexibility since you would be able to pass in different types of values at the same time: s.list1 = "cat1:val1,,-t2:val2,etc."