Oh that is a good idea! I hadn't noticed that you could just provide an entire XDM object at the root of the Update Variable action. That makes a lot of sense. Thanks for the response, I've added a note on the blog

The new Update Variable action in the AEP Web SDK extension would be a lot more helpful if you could start with an existing XDM data element and update that, rather than having to start with an empty XDM object every time.In the scenario where you’ve got a lot of fields that you want to set on every...

I've written a script to automate most of the steps outlined in the original blog: https://github.com/station-10/adobe-usage-import-public

Nice!

Just want to point out that while the Adobe Analytics Product String extension is a step in the right direction, the version currently available doesn't support merchandised evars or custom events so is of limited use

Ah perfect, yup that works! Thanks

The Launch documentation suggests that the _satellite.track() function can be used to pass along extra information in the syntax:_satellite.track('contact_submit', { name: 'John Doe' });However when I access this detail object using %event.detail%, the element is resolved as "[object Object]"Have I ...

Just come across this issue too, thanks for flagging it but seems like a bug that should be fixed.In order to fire an scAdd event should I have to manually add products to linkTrackVars in custom code, or should Launch handle that automatically?

I've also got this problem, tried the solution and it fixed it

In order to keep my list of evars and props in a sensible numeric order, it would be really great if you could rearrange the list. Or let us sort the list by number.