I'm trying to understand why AppMeasurement places list variables high up in the image request. In s_code, list variables were included near the bottom so that if the list variables became very long it was less likely to truncate other variables in the image request. This is not true in AppMeasurement and I am seeing other props and eVars not being captured when the list variable is very long. Is there anything I can do to help in this situation?
when the image gets long appMeasurement code is supposed to flip over and send POST requests instead of GET requests. The debugger will show 'no requests found' in red text but if you go into developer tools on your browser and look in the network tab you will see a POST to you metrics server (instead of a GET) request for the image. You can then pull that request and uudecode it and find all the props/evars
I know I had (and still have in some instances) a list variable with several hundred entries in it and everything gets sent
Ah that is good to know. In my particular situation, the image request is sent from a container app on an iOS device. I wonder if the switch to POST happens the same on mobile? I'll have to check it out!