Activity Map Issue

[bindukumari90]

Hi Team,

Currently we are using v26 of websdk extension and facing issue with external and download links i.e.

External link is passing payload data only if external link is opening in new tab, if it is opening in same tab then collect call is firing but not passing payload data and data is not coming in reports. So, is it right?

For download link, collects are not firing.

Is anyone facing above issue for the same

[bjoern__koth]

Hi @bindukumari90 

can you paste a sample markup of a link of yours? There are some constellations where ActivityMap won't fire.
Just trying to reproduce it.

[bindukumari90]

For external links:

if you click on any external links from, for example careers as shown in below image 

For download links, suppose if someone clicks on download and it downloads the pdf file but still no collect calls fire.

[bjoern__koth]

HI @bindukumari90 

I can see both WebSDK and AppMeasurement firing analytics requests on your website?

Presumably, you are having Activity Map also installed on Web SDK side?

Not sure whether these two could potentially interfere with each other.

Have you tried disabling either the module in AppMeasurement or in the WebSDK Launch extension?

[bindukumari90]

Yes, but for testing we are using separate property which has only websdk extension, I am testing through injecting library via AEP debugger.

Is this behaviour which I have given is expected or it is bug?

[bjoern__koth]

Hi @bindukumari90 

can you append a screenshot of your Web SDK's "Data Collection" section in the extension?

Also, are you using and kind of custom code in the "Edit filter click properties callback code" code section?

[bindukumari90]

For external link, if it is opening in different tab, then collect call is firing but payload is not collecting the data.

For download, no collect call is firing

And, we are not using any custom code. Below is the seeing websdk data collection:

Thanks!!

Bindu Kumari

[bjoern__koth]

Seems you have Event grouping enabled. This will store your clicked element in the session storage and only release it on your own domain's next website and only if certain additional XDM fields such as event type, web.webpagedetails etc are set.

There have been a few threads about this lately. In this thread I give a step by step description: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-platform/eventgroupingenabled-web-... 

to validate, can you disable the event grouping and check if it works as expected?

[bindukumari90]

Yes, I have tested without event grouping it doesn't work, it creates separate collect call.

So, by reading thread it tells about internal links because session storage for internal link, but for external and download why it is behaving in this way i.e. external links firing payload when it is opening in new tab and download links are not tracking only through websdk extension.   

[bjoern__koth]

Have you checked if the requests are maybe attempted but aborted in the network request? There is always a "preserve log" checkbox in the network tab to keep the requests from the previous page.

aborted requests can happen when a page navigation occurs and open tracking calls have not fully finished execution 

[bjoern__koth]

@bindukumari90,

can you, just for testing, add code to the filter click properties custom code that logs the properties in there? This should give us an idea whether the activity map fires at all.

Just anything that is listed in the commented code there would surely help