Hey, so in Activity Map, is it fair to say that it always sends data about a click on the next /b/ss/ beacon? More specifically:
With a Download Link or an Exit Link, is the click to that going to show up on the next /b/ss/ beacon (so not the actual Download Link or Exit Link beacon, but the next beacon)?
What about for links that open in a new window? If that page has AA and is on the same implementation, it's going to show up on that page's load, right? What if that next page isn't on the same implementation though?
Are there scenarios (like Download/Exit links or new links that take you to a spot where the same implementation of AA isn't) where the Activity Map data is lost because there's not another user interaction and so therefore no subsequent beacon?
If a link is clicked, the data is collected, however, if there won't be any server call firing next (for example, from the next page without any Analytics implementation), the data won't be sent to our servers. However, whenever a beacon will trigger to our server from the same browser (in the same session as s_sq is a session cookie), the data will be sent.
Your understanding is correct. As soon as a link is clicked on a page, the Activity Map information is collected in s_sq cookie within the browser. The details are sent to our servers in the Activity Map context data parameters in the next web beacon.
In case there is a link that doesn't load a page or trigger a server call, the Activity Map data will be stored in s_sq cookie and wait for the next server call.
Thank you for your answer. Just to be clear, based on what you're saying, if the user clicks a download link, exit link, or a link that opens in another page that doesn't have the same AA implementation, AND takes no further action, that Activity Map link click will never be collected, correct?
If a link is clicked, the data is collected, however, if there won't be any server call firing next (for example, from the next page without any Analytics implementation), the data won't be sent to our servers. However, whenever a beacon will trigger to our server from the same browser (in the same session as s_sq is a session cookie), the data will be sent.
