What happened to the Adobe Cloud debugger?  It is no longer in the Chrome store

When will Launch be upgrading the extension to use at.js 2.0 (or higher)?

Thanks. Looking forward to seeing it.

I just saw this and frankly it is useless. Almost all of my rules use custom code and the comparison screen shows my code minified and all on one line.I need it to appear as it does in the code editor.

This cannot be done thru a processing rule unless all the individual pieces are being sent at the same time. I would suggest using a custom variable, e.g. an array to capture all these values and then send them concatenated prior to when the user navigates away from the page or closes the browser.

I don't think you can do what you are proposing. I think it is a 1:1 relationship with direct call rules (and possibly 1:many). Meaning that each direct call will have to have at least one rule attached to it. I also don't think there is any way of referencing the trigger event.  What I would do is ...

I get the same result, but out of curiosity why not use object literal notation?  var test = {};

Aaron,Can you clarify accessing the event detail?  If I do this _satellite.track('home', {'name':'John'})console.log (event.detail.name)  is invalid - no detail property.Thanks

If a rule or data element fails I would like to see more robust error messaging in the build screen, e.g. which rule or data element failed rather than a generic failed message.

When I use ES6 keywords such as const or let in my code the linter gives a warning and the build fails.  How do I go about fixing/addressing this?Thanks