Thanks for the question Dave.hamel​. The reason the Device Type condition is no longer supported is largely because the definition of certain "device types" has become very blurry in recent years. For example, what do you consider "desktop" these days?If the device supports a mouse instead of touch?...

The code is complete for this, but Adobe is going into a blackout period where we won't release new code during the holidays unless there is a critical issue. Because of this, the feature is set to be released in early January.

I have a few questions:1. Is your custom code JavaScript or HTML?2. Is the "global" checkbox checked in custom code action?3. What issue(s) are you noticing with the code being inserted into the DOM each time the custom code action is run?

Thanks for bringing this up! I can confirm that this data doesn't get passed through currently, but there's no reason we can't support it. I'll put it on our list.

Supporting the renaming of _satellite would be the easier part. The more difficult part would be avoiding conflicts in persistence layers (e.g., localStorage, sessionStorage, cookies) and conflicts in in-memory objects (e.g., the same extension in two properties loading the same library twice).I bel...

You should not use _satellite._container in production code as the structure will very likely change over time (if you have debugging turned on, you should see a warning message to this effect). _satellite.property and _satellite.buildInfo are fair game for production code, though. As Josh said, _sa...

Thanks for the good conversation around this. joshd7227840, I believe your request concerns the Adobe Analytics extension specifically; nothing in the underlying Launch platform prevents it from happening. Right now the owners of the Adobe Analytics extension could provide a textfield whereby you se...

If you choose "any element" in the Custom Event configuration view, the rule will fire when your custom event is triggered from any element, including document (but not window). Does that suffice for what you need?

This hasn't been documented yet, but you can access the rule name by using %event.$rule.name%

Could you send me a URL to your library please?