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=...
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?
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.
eVarXX = "product catalog";
listX = "product A,product B,product C";
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.
use list prop to set code (abbreviation) value and classify prop with auto classification rule builder to get full details for set code.