Can the same be assumed for Target and using es6 in experiences?

mikem2436009​ - I am working on investigating building this out in our stack (still DTM, not Launch)Basically if you integrated ftp hosting into your version control system, this may be possible. I would suggest using commit hooks and a build server to trigger shell scripts. perhaps we can share on github?-AJ (notdefault@github)

satelliteLib-7998b06......js is your library, that's where all of the code will execute from, so yes, you should see that in the console. if you see "errors" coming from this script, then something is blocking it or stopping internal execution and the beacon wont be sent. in the network tab, if you filter requests for "/b/ss" you will filter only the beacons that are sent to tracking servers. The data being sent will be in the parsed/decoded query string. the target server will be your tracking ...

Adobe will have to speak on SLA and response times from their servers, but by default content I mean 'the front-end application', NOT Target. Are you using the akamai hosting or DTM? more often than not, the adobe server response times are a non-issue.

Jantzen.Belliston​ -- do you by chance know if Launch can integrate with GIT or version control systems, or be fit into a continuous-integration cycle?

your data elements should be referencing specific objects on your data layer, not treating the whole data layer as a string.Assuming that dtmAnalyticsData is your data layer, does it follow any specification?example: https://www.w3.org/2013/12/ceddl-201312.pdfin your data elements, you can reference by `JS Object` to window.dtmAnalyticsData.{specific_key} to return a value.Then in your rule, configure an evar, prop to use those data elements.