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

Here is some adobe Docu they sent. Embed Code and Hosting Options

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 ...

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 ...

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 experience will not be rendered, but normal default content should still be processed and rendered as expected. at.js is a library to support your experience, it is absolutely required to be in the header. The modifications to page content YOU control via the target interface. as far as i know ...

you can pipe your data layer value for country into a global mbox param, then use that as part of your audience targeting within Target.See Adobe Docu here:Mbox Parameters And: Behavioral Targeting

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...

It looks like you're already capturing event40 on click of any star, I would just use js to determine which n-th chld (star) was clicked, or add .star-1, .star-2, .star-3... as classes on each star for exact determinationThen once you know which star, pipe that into an eVar or prop on the event40 ru...