So after some ping-ponging with Adobe support, they checked internally and came back with this responseClose Case Comments: The query was productListItems SKU and name, and as per current logic, SKU is a required field. When using in WebSDK, the same value can be passed to SKU which is passed to nam...

Hi Madhan to be clear, I am using the automatically applied mapping of the XDM's productListItems to the products string via AEP, no "s" variable available since everything is being handled through the Experience Platform.   So this should work out of the box, or at least the SKU should be optional ...

Hi folks   using XDM to ingest Web events data into AEP we noticed that the product SKU seems to be used to generate the Adobe Analytics "products" string which makes little sense if you have a numeric string instead of the actual speaking product "name".   Looking at the documentation here https://...

Hi @Anil_Umachigi  spoke to Adobe as well and they suggest the same. They also indicated that it is on the roadmap to bring Profile (and consent) information in the event forwarding in the near future, so this is just a temporary workaround. BR Björn

Hi all   I am fairly new to event forwarding and have a seemingly trivial question. So, we have an AEP setup that sends an alloy("setConsent", ...) as soon as the user consented.   Now we have the task to implement the Facebook Conversion API via event forwarding in a Launch Event Forwarding Propert...

Hi @shayo28675173    thank you for the detailed answer. It really helps to understand the problem a lot better resp. confirms the knowledge and assumptions contained in this thread from an official Adobe perspective. As mentioned earlier, if this is a known issue, I think it would help many develope...

But how can this not be treated as a road block since it is obviously also resulting in massive additional server calls to AA which then will also increase the cost on client side? I am really struggling to understand why this has gone so long under the radar and if it has been fixed once, then roll...

Oh my, they could at least point this out somewhere in the WebSDK setup's configuration and provide a standard piece of code like prehiding snippet for Target / Personalization. Just something that indicates that actions need to be taken.   Anyway, thanks for the update!   BR  

Hey guys, this seems to have been unresolved for a long time and a workaround is not a fix.   Has anyone received any update from Adobe on this since I am, more than a year later, having exactly the same problems and can imagine that pretty much everyone else has who is using Target mboxes in conjun...

Thank you Anil, that helps a lot! Just looks funky that Adobe is missing out this "little" piece of information in their XDM schema so you are practically forced to pass in the whole array of product objects (fair enough, who wouldn't :D)  Cheers Björn