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...

//try thisdigitalData = {  "cart": {    "item": [{      "productInfo": {        "productName": "productName_1",        "productstyleNumber": "productstyleNumber_1",        "productID": "productID_1",        "productCategory": "productCategory_1"      },      "quantity": "3"    },{      "productInfo"...

Would you mind providing an example of the data layer JSON object? Would you mind providing the AA requirements? events, and evarsWith this, I can get you pointed in the right direction.

Yes, The same hashing function (SHA256) can be used on the keys within your CRM so that you can make the connection between the hashed values in your analytics data and your customers in your CRM. Here's how I would do it in R. Take note that I'm applying the same data normalization (force to lowerc...

Hi Thomas, You may find this tool useful as you are making your DTM to Launch migration roadmap. It will identify things in your DTM codebase that should be addressed prior to moving to Launch.  It identifies things like deprecated functions and incompatible references in your DTM custom code. These...

Yes. I have done this too many times to count.Custom JS is probably required.To be more helpful, can you answer a couple questions?1) Do you know where the cart item data exists on the page?2) Are you lucky enough to have this data in a data layer that can be easily accessed from JavaScript?3) What ...

I'm a little late to the conversation, but I wanted to chime in to add that the SDI Toolkit extension provides Launch Actions for setting and removing sessionStorage and localStorage values. 

I don't disagree with the guidance of using the AEM context hub extension, but I wonder if it's more trouble than it's worth in your case. Since your data appears to be pretty flat, you _could_ just create a Launch data element for each value that you care to access. To do this, you'd :1) choose "Ne...