For what it's worth, while Mobile Screen Size pulls from user agent and is wrongly getting lumped into 320x480... "monitor resolution" still pulls from the "s" param in beacons, which comes from javascript objects in the browser, and seems to still be correct. I believe this only works for javascrip...

@aahardy That would be slightly better, but the problem is that users are often on another tab (or off grabbing some coffee or something)- if they're inactive for long enough to auto-logout, they're probably not going to be there for the warning either.

At bare minimum, auto-save before log out!

Intriguing, thanks for letting me know! I'll have to test and see if this has, in fact, been resolved!

Can I add my vote for making this something we could disable? Especially since our options for copying and/or cleaning up values in Launch or in Processing rules is so limited.

Unfortunately, the Adobe Media Analytics extension does nothing more than set up the heartbeat code and instances.... it does nothing to actually track anything, and the documentation is SEVERELY lacking. :/

This is similar to Display more information in the rule overview .

It'd be great if when _satellite.setDebug(true) were enabled, you would get additional information about the _satellite.track functions and Custom Events that are firing. I described an external workaround/fix in a blog post (Enhanced logging for Direct Call Rules and Custom Events for Launch/DTM - ...

I would love this as a native thing, but FWIW, you can use Tagtician for this: Tagtician: Adobe Launch & DTM Debugger - Chrome Web Store

That makes sense. But most of the time, extension upgrades do not directly affect any of the things users are asking the extension to do- they're for bug fixes, or minor UX enhancements, etc. For instance, if I'm on Adobe Analytics Extension 1.7.2, and set prop7 to some value in one rule, then upgra...