Possible to get more than just 3 list variables? Or how to work around it? | Community
Skip to main content
Level 2
December 23, 2020
Solved

Possible to get more than just 3 list variables? Or how to work around it?

  • December 23, 2020
  • 2 replies
  • 3624 views

I work at a big company where the marketing department wants to track all projects within the same report suite.

We need a list variable in our project, but since there's the limitation of only 3 list variables per report suite, and they're already used by other projects, what are our options besides hacking a work-around and using the product variable? (list props won't work either due to the 100 char limitation). Can we pay to buy more list variables or why is this not possible?

"An organization can have many report suites, each containing different data sets. While separate report suites were important in the past, having a single report suite has become more advantageous" ~ https://experienceleague.adobe.com/docs/analytics/admin/admin-console/create-report-suite.html?lang=en#admin-console

I guess the marketing department agrees that it is indeed an advantage for them to keep all projects in the same report suite, but from a developer standpoint, given the 3 list vars limitation - how is this advantageous?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by yuhuisg

I think the number of list variables is a limitation of AA's data store backend. So there's really no way to get more, even if you're willing to pay more.

Are all 3 list variables already in use? If there's one spare one, you could do the following: track it with another eVar, where that other eVar indicates the purpose of the list.

E.g.

eVarXX = "product catalog";

listX = "product A,product B,product C";

 

and

 

eVarXX = "internal promo banners";

listX = "banner 1,banner 2, banner 3";

 

Then when reporting listX, you'd always want to report it with eVarXX so you know what values to get back.

2 replies

yuhuisg
Community Advisor
yuhuisgCommunity AdvisorAccepted solution
Community Advisor
December 24, 2020

I think the number of list variables is a limitation of AA's data store backend. So there's really no way to get more, even if you're willing to pay more.

Are all 3 list variables already in use? If there's one spare one, you could do the following: track it with another eVar, where that other eVar indicates the purpose of the list.

E.g.

eVarXX = "product catalog";

listX = "product A,product B,product C";

 

and

 

eVarXX = "internal promo banners";

listX = "banner 1,banner 2, banner 3";

 

Then when reporting listX, you'd always want to report it with eVarXX so you know what values to get back.

Level 2
December 27, 2020
Thanks, at least this is the best workaround I've seen suggested. I guess I'll have to see if I can get a list variable free'd up, so maybe we can use this trick. A little surprising however that you'd have to go this creative to make it work 😄
Asheesh_Pandey
Community Advisor
Community Advisor
December 25, 2020

use list prop to set code (abbreviation) value and classify prop with auto classification rule builder to get full details for set code.

- Asheesh
Level 2
December 27, 2020
Unfortunately we need a lot more than the 100 bytes that is supported in total for list properties