If you've not referenced the cross-domain documentation, I'd recommend starting there. https://developer.adobe.com/target/implement/client-side/atjs/atjs-cookies/?lang=en As with any cross-domain implementation, you've got to get the identifier to that new domain. In your case, is there always a pathway for the user to get from domain A to domain B? Can they enter on either domain and navigate between domains?

There is a lot that could go into this. Tracking will be dependent on the browser used and the implementation of cookie consent manager. I.e., if Target cookies are classified as personalization and the user opts out of all but required, then their activity likely shouldn't be tracked.

A failed action is a partially failed application of the experience onto the page (Mbox). You can see an example of what that looks like in the post here. For example, I have an experience that replaces a good majority of the content on a specific page. I have a script like the following to check for and send associated activity information to the dataLayer, but that only checks if the Adobe Target request succeeded and what it got back. It doesn't tell me that the experience was successfully ap...

@Amelia_Waliany , I somehow missed this one. Usually I get an email notification or something. Is there a list I can sign up for to be notified of future coffee breaks?

I had not, but I'm putting this on the todo list! 

HI @davidl55903031 , I'm basically doing the same. I loop through all of the activities and send an "activity view" event to Google Analytics. For each activity, I loop through the links and build a click listener using a data-adobe-target-click attribute that I add the to the experience code. I have noticed some issues with colliding experiences, but can untangle those with specific activity ids built into the listener and in slicing data during analysis. Like you said, not an ideal solution! I...