I totally agree with both Jennifer and Bjoern that we should keep it simple and not try to tag everything. However, they do want to see that interaction going to downstream datawarehouse to be able to do more analysis and optimize inventory. Will push for having a trade-off. Related question : Is th...

We have multi select values in each element . I like pair:values in list vars. Where do I pass the list vars - in the page view call (so every time user interacts with an element a page view call is triggered)? User clicks on element 1 value 1> Trigger page load call > Pass in an evar X= element 1:v...

Also, if my link click is leading to a next page right now we are triggering a link call (other) and also a page load call. I dont think we need the link call. We can only trigger the page load call and in that call pass a variable that shows which link was clicked on. Is this the best practice? Any...

This is fine. But how do I know that user interacted with value X (in element 1). This is needed to optimize the page element. Is there any other way to know/track each and every element of the page without triggering the server calls? I dont mind a refresher on product list variable and on merchand...

We do want separate evars, events so that we can get those variables for downstream reporting so activity map will not work. We also want to track every element to understand the user's engagement. Is there any example e-commerce retail site (based on app measurement implementation) that anyone can ...

Do you have any documentation that shows that we can get click throughs for list vars?

What is the best practice to tag every clickable element on the page? Especially on the checkout page where there are payment options plus delivery information etc. Right now our site A triggers link call for every interaction by the customer. I dont think this is the best way. Is there any guide (e...

Thank you Jennifer. In my first query, I am seeing variables on the page which has null values. That is why i am referring to them as redundant variables.  In the second query, I am talking about a list var (that behaves like an evar). Right now for every default selection, link call is triggered wh...

I have analytics questions.1. What is the business impact if we pass redundant variables (props and evar) with page call and "other" link calls?2. If I pass default selections (that loads when the page loads) in a list variable in the page load call, can we get clicks/click through for these values ...