Try this one:https://chrome.google.com/webstore/detail/adobe-experience-platform/bfnnokhpnncpkdmbokanobigaccjkpob For some reason the old one was pulled from chrome/play store. Got the above link from slack channel.

We ran into something similar with click tracking mboxes in target. our solution was to override the onclick and href values of the element clicked, then in the success AND error states of the click tracking call, we then created a new dom a tag on the fly, added the href back for the next piece of js to use the window.location change. works well, kinda hacky, but that's what we had to do in order to deal with the window.location changes better way is to not do the window.replace and instead rel...

you might find more information referencing cross-domain with GA in google groups, since this is a DTM forum and your adobe setup seems to be working.. not sure what the question is. I don't believe there's anything dtm or adobe analytics can do to help with how GA records visitors. personally i wouldn't piggy back either platform on each other. if you need both, then run them in parallel, but understand that tracking will always behave slightly differently.

On a dynamic SPA site that I'm working with right now, we have no server generated data layer. however, I've added two sequential scripts that first: defined window.digitalData and some assumed static properties. The second uses Object.assign() to merge a new object with actual data into the existing digitalData structure. This enabled a semi-dynamic data layer, that was created at pageload, but before the initial pageBottom trigger was fired.

use defensive coding in your data elements when referencing data layer object properties, to see if the data object properties exist before you try to reference them.Also, dispatch a browser event when the object is added to the array and pass the data in an object with the event. Listen for this new event with DTM