Search Discovery Adobe Solutions
Search…
Adobe Solution Docs Home
Adobe Launch
Launch Extensions
DTM to Launch Migration
Common DTM to Launch Migration Issues
_satellite.buildDate
_satellite.data
_satellite.cleanText
_satellite.getDataElement
_satellite.getQueryParam
_satellite.getQueryParamCaseInsensitive
_satellite.getToolsByType
_satellite.getVar("event.*")
_satellite.getVar("param.*")
_satellite.getVar("window.*")
_satellite.isLinked
_satellite.isOutboundLink
_satellite.loadScript
_satellite.notify
_satellite.publishDate
_satellite.readCookie
_satellite.removeCookie
_satellite.replace
_satellite.setCookie
_satellite.settings.isStaging
_satellite.tools
_satellite.QueryParams
_satellite.URI
_satellite.URL
Chrome Browser Extensions
Launch & DTM Switch
SDI Auth Bridge for Adobe Launch
Powered By GitBook
_satellite.tools
We don't know why this would be referenced in DTM custom code, but it was... It was always an internal object that contained information about the tools in use by the DTM property. As an example, here's a snap of _satellite.tools from a sample DTM property.
sample view of _satellite.tools object
What were "Tools" in DTM are "Extensions" in Launch. Launch exposes information about the installed extensions via _satellite.container.extensions. Just for parity, below is a sample snap of this object.
sample view of _satellite._container.extensions object
(as of 8/19) _satellite.container.* is still marked as unstable. If you need to reference the data in it, do so with caution. Stability is coming soon.
​
Previous
_satellite.settings.isStaging
Next
_satellite.QueryParams
Last modified 2yr ago
Copy link