Hi, I couldn't agree more with you on he dataLayer comment. I'm guessing you like me have been through the pain of objects not updating in time for the call! :). I remember one install having to to have a direct call which fired another direct call but delayed for 200-300 ms... Fortunately we worked with dev to get that sorted.But interesting we have two different views on SPA tracking.

Thanks for your help Steve, we're up and running. One final question if I may;I'm having a bit of an issue with the product string, I can see the contents of the product string if I set a processing rule for products(Context Data) it to an s.prop. However this is not making it's way to the main product dimension. Is there anything obvious in the call below which would suggest it's not being set correctly in the app call?AdobeExperienceSDK DEBUG ]: Analytics request was sent with body (ndh=1&c.&a...

Thanks Steve, that makes sense. We we're under the impression that things like launches would be pushed without the need to set. We'll add some in and update this post.

Hi,We're just in the process of upgrading to Launch and need some clarification on your pointDTM staging endpoint will remain and code on it will remain. As far as I know there is no plan to delete the code. It is a good to use the staging DTM endpoint against the Poduction endpoint to do performance analysis. We have seen an instance when we migrated where to website went from 24s to 6s load time. (Yea DTM blocks a lot).So this means if we using the 'Upgrade to Launch' option only production is...

s.purchaseID should do the job without having to serialize an event... Unless you're using some random number for s.purchaseID?

Hi, how did you get on with this in the end? - We have a 3rd party implementation which can only push GA events on user activity. However we only use DTM. Can we 'listen' for these GA events using DTM?