Has anyone been able to get this to work? I have code that is firing an event and a rule set up with a CustomEvent trigger listening to it. I have tired all sorts of different combinations with no luck. I wrote a listener by hand and it is getting invoked, so I know the event is being fired.I could never get this to work the way I thought it should in DTM, either, so maybe Adobe and I have different ideas on how to handle events...Anyone have an example or some tips?

I know Extensions have shared modules where they can be shared with other extension code. Can the same structure be used in a piece of custom javascript code deployed as an Action?We have been developing a set of utilities (similar to what we did in DTM) that we are calling "Useful Things Adobe Should Have Cooked Into Launch" (granted, it needs a less unwieldy name!). We can load in in custom JS and make the functions available at the window level, but if we could cook it all into an Extension i...

A couple of us are working on developing rules changes in different DTM properties, and both are seeing the build date get updated when we reload our pages, but not all rule changes are being included. We use Akamai for our DTM files.I have had this happen with both Direct Call and Page Load rules. Sometimes I can make a minor edit and get the build to pick it up, but that does not always work.We are at a standstill.

Will the _satellite.browserInfo object be available in Launch? Our current implementation utilizes this information in many places, giving us a common definition for browser, OS, device, etc.

I've searched around with no luck, so I am asking here...I am pretty well-versed in the s_code and AppMeasurement,js ways of doing things, but am still new-ish to mobile apps.When a user clicks a link inside our app that takes them to a mobile web page, I would like to record that like a lnk_e would on the web. Is there a way to set the app equivalent of linkType in the trackAction() or trackState() calls?Thanks -Jim

We have been using the MC Visitor ID Service for some time now. When we first hooked it up, the advice given regarding setting customer ids was not to bother because they weren't used for anything at that time. I found this same information on some blogs written by Adobe folks and in talking with our internal Adobe contacts.Is this still the case? It seems that if I associated, say, my customer'd account number with the the call that the service could use that to associate that same user across ...