It would be useful to have some tiered access control on Launch rules (and perhaps data elements). I would like to be able to create a baseline set of rules that can be viewed by others but not changed. The scenario for this is an environment where Launch is triggered by various application events s...
I see the same thing. My guess is that they want to encourage async deployment as the default best practice (A stance with which I happen to agree). I am also pretty much in agreement with your list of pros and cons. The point about _satellite.pageBottom() is a little nuanced though. My understan...
thomas.amsler - You hit the nail on the head with, "the code is publicly reachable." The assessment is just a free service that we are offering up to the community. We are doing it to be helpful, but also to be visible as having expertise in the space.
read.csv is actually an R function. It pulls in the file, /Users/Eric/Documents/R-Data-Files/custID.csv and puts it into a new data frame by the name, sampleCRMdata.The file, custID.csv, can have as many columns as you want as long as it has one column with a header of "custID".
I know that this was basically impossible to do in DTM, but I'm wondering how feasible it would be to allow the property administrator to configure Launch's primary object from _satellite to another string so that multiple properties could coexist on the same page. My reason for wanting this is to a...
Then in the AA custom code of your cart view rule, you'd set s.products as such:s.products = _satellite.getVar("_your data element here_");It's worth noting that since you presently cannot set s.products from anywhere except in AA custom code, you _could_ just use the code above and set s.products d...
Much of the code is just for exposition (to explain what I'm doing). For your data element, you'd paste just this much and add a return line as such: var cartItemCount = window.digitalData.cart.item.length||0;var productStanzas=[];for (var i=0; i<cartItemCount; i++) { var cartItem = window.digitalD...
This is the general idea based on the requirements for an Adobe product string: A couple notes. 1) I was not sure whether you wanted to use productName or productID in stanza[1]. I chose productID as it's typically a better identifier than product name (which might change over time or due to local...