@jantzen_b unfortunately the issue has not yet been resolved, while I do appreciate the efforts made on this thread. At the time of writing we are in contact with Adobe's engineer team. I figure I could post the solution before I mark this has resolved.

@vibhatna sorry for the lack of update. We still have some issues - the changes you suggest ed did help us see revenue etc. in the real-time report, but for some reason we can't see it in Workspace! We're currently in touch with Adobe, who are looking into the issue. I'll keep you posted once we've ...

@vibhatna Quick question: We're using Swift so the syntax looks a bit different. Can you by any chance verify is this is the same as what you propose? https://gist.github.com/jacobsander/9ae6c419a63fd44eea7ae5b694a3d533

@vibhatna Thanks so much for your reply! I'll give it a try and let you know 

https://gist.github.com/jacobsander/b0c5c0168046179e6a34a3a1f1ba8c7b

I'm pretty sure we're not executing step 1 or 3 from the guidelines correctly, but unsure what the code should look like to work

Hi @amgup, thanks for your prompt reply! I'm having trouble sharing my code - hope you can see this gist: https://gist.github.com/jacobsander/b0c5c0168046179e6a34a3a1f1ba8c7b

According to Adobe's docs, you set the currency code via the following steps: Set the currency code in a context data variable during either trackState or trackAction.Create a processing rule in the Adobe Analytics admin console for the report suite. Set the rule to overwrite the Currency Code varia...

Gotcha  thanks so much again!

That makes sense  so in order for it to work via the extension, we would have to push currency to digitalData on every page load essentially?