I would suggest posting an idea to cover this line from your first post, instead of renaming the _satellite object."My reason for wanting this is to allow a configuration where two or more Launch instances are deployed on the same page."
Have you seen the reference implementation guides? There is one for angular.Adobe Launch Reference Implementation Guides: https://helpx.adobe.com/experience-manager/kt/integration/using/launch-reference-architecture-guides.html
Let's back up a step here. Create a simple page load rule and set an evar to a test value. Let's make sure that Analytics car fire the beacon from your beta environment, and that we can see the beacon in a debugger of some flavor.
Just to clarify, you are looking at the staging library right? As of now when I look into the account I do not see the rules as being published to production yet.
You can reuse variables but not in the way you are thinking. Setup Data Elements within DTM to do this. You can have a Data Element named "ProductID". Then within analytics you set eVar1 (or whatever variable) to %ProductID% and then you can use that Data Element for any other var or tool or tag ...
I second the notion that having more than 1 TMS on a site is not generally a good idea. However if you are forced down this path there are a few things to make sure you are doing / not doing.1) NEVER EVER EVER use one TMS to deploy another TMS. It's bad mojo.2) The success rate of having code in o...