Expand my Community achievements bar.

Join us on September 25th for a must-attend webinar featuring Adobe Experience Maker winner Anish Raul. Discover how leading enterprises are adopting AI into their workflows securely, responsibly, and at scale.

Improve logging for Direct Call Rules (and maybe custom events?)

Avatar

Adobe Champion

6/10/19

It'd be great if when _satellite.setDebug(true) were enabled, you would get additional information about the _satellite.track functions and Custom Events that are firing. I described an external workaround/fix in a blog post (Enhanced logging for Direct Call Rules and Custom Events for Launch/DTM - 33 Sticks ) but basically, right now for a Direct Call Rule I can either know it fired, or its string wasn't found as a Direct Call Rule trigger:

1769829_pastedImage_1.png

But now that folks can send extra params with more information, it'd be great to see more details- something like this:

1769830_pastedImage_2.png

Something like this would also be wonderful for Custom Events, though I understand that would be trickier because Custom Events are far more, well, custom- I'm not sure how you would listen to them if they can have any name and be bound to any DOM object- but that would be very helpful.

3 Comments