The benefits of list variable is that you can store any type of value and classify them.   So use syntax like var1:value|var2:value2|var3:value3,value4 Note: I consider | is the delimiter configured in list var configuration view Then in classification configuration for listx create a report for var...

these data are generated post collection so using post-processing. As I said they are linked to user-agent. Never heard that we can't collect them. User can opt-out from analytics but that would mean you cannot collect any data and will have to stop analytics collection based on their cookie selecti...

They are 2 ways to implement mobile apps for Adobe Analytics:   Solution 1: point product implementation In this solution you will need to install the Adobe Analytics extension and use the trackState and trackAction from the MobileCore extension https://developer.adobe.com/client-sdks/documentation/...

This is what you are looking for https://developer.adobe.com/client-sdks/documentation/identity-for-edge-network/api-reference/#geturlvariables  

#1 Ask you developers to emit an event when popup is displayed   #2 Is there an event pushed inside your data layer when popup displayed ? if not that would be the best option   #3 MutatioObserver: https://developer.mozilla.org/en-US/docs/Web/API/MutationObserver bit of a heavy solution but works ju...

I think you might want to track list variables. This will allow you to add unlimited amount of data and they will each be break down on one line item. Also you can apply classification on each independent value.    Check this https://ecapacity.com/embrace-the-power-of-a-hidden-gem-in-adobe-analytics...

As far as I know device info and browser info is not PII data. Just by looking at this data you cannot identify a specific user. Based on that it should be fine to track this data.   Also browser info and device info are derived from the User-agent as far I believe

1. Do you need this function ? I find that writing my own plugins is safer, also adobe launch can do a lot of things nowadays without relying on plugins 2. Did you check it is latest version of plugin ? 

Ultimately best way to track this would be to have a data layer and your developer should push an event each time new product list is displayed

I think you should move the requirements away from scroll depth/percentage to component/page loads.   I would think your app might work in a way that it would fetch N amount of products and display them, when it reaches the end of the component a new request is done to fetch next N amount of product...