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%