Yes, that's exactly what the direct calls do.In the above case, your javascript/jquery creating the would make a call: something like _satellite.track('xyz'). In DTM, create a direct rule and for the condition put xyz and fill out the adobe analytics portion of the screen like you would with any other rule. As you stated, you can pass in values for your props by having a data layer (just make sure to set your values before making the track call).The training video gives a little background: htt...

Going from something on Search Discovery's FAQ, it looks like the elementexists may only fire when an element enters the DOM (otherwise, the rule would probably just firing over and over since it continues to exist). It's hard to tell without seeing your code, but if the .errorflag element is already in the DOM from the first trigger, maybe that could prevent it from triggering the rule again?Could you also maybe approach it the other way and make whatever is triggering the error span to appear ...

Eric,Rather than using the built-in integration you can try to use a third-party tag with sequential HTML triggered on top of page that uses a more traditional mboxCreate syntax (this is obviously a bit different than the "create mbox around" so you may need to adjust accordingly). mboxCreate("xxxxxx");

You can change the expiration of your data element from "page view" to "session" within the UI and the value should persist when you get to the next page.

I think there are advantages of both. What I think could be useful is if you kept the draggable rail like it is now. And then, if you hover over an entry in the table, it gives you an icon where you could get the navigational like the breakdown link does in a normal report (kind of like how the filter icon shows up if you hover over the dimension).