I would like to see the %data_element% syntax expanded to be able to reference properties of returned objects.  For example, currently in DTM you can do %data_element% syntax in various fields.  And for certain built-in data elements, you can e.g. %this.id% (reference to a clicked link's id attribut...

"Working as designed" what a copout b.s. answer.  I think it's literally everybody's expectation that the rule tester should show you exactly what you will end up getting in the reports. And if that is somehow not Adobe's vision of it, then I strongly recommend Adobe change their vision.   Better ye...

I'd like to extend this to also (un)check the ActivityMap module.

A couple of years ago there used to be a "page view" expiration, distinct from "hit", which worked for the scenario you mentioned above.   But then for some reason Adobe decided to get rid of that expiration option for reasons unclear to anybody.  It would be nice if they brought it back, but for no...

Hello Eric, Yes, that is what I do as well. However, a couple of things to note: a) having to do it the "legacy" way kind of defeats the purpose of making things "friendlier" with a tag manager b) Up until (relatively) recently, it wasn't even possible to make use of doPlugins in that manner. You se...

Yes! This is one of the MANY problems I have with integrating AA as a tool in DTM.  More often than not I find myself with a choice of a) implementing AA as a tool but with lots of nasty hacks/workarounds to get around a TON of wtfery with DTM vs. AA, or else I implement AA as a 3rd party tool and l...

@Julian  -  you can request Adobe to scrub data you don't want. I've been through it a couple times with several clients. I do not recommend it unless it is super business critical, like.. accidentally sending Adobe customer passwords or cc#'s or other extremely sensitive/private info that will get ...

@AndyW - Actually no, we cannot do case-insenstive matching.  CRB is case-sensitive.  A couple years ago when CRB first came out, the regex tester popup (where you enter in the regex and a single key to test against) was case-insensitive.  But when you go to the rule tester (where you enter in multi...

why not all of the options? make it similar to scheduled reports

I don't know the backend setup but I think maybe one way to approach it would be to have a single contextData report where under the hood it's basically a prop, and then the keys/values would be handled similar to saint classifications. Since there a one to many relationship with key/values, the val...