Adobe Analytics : Multiple Experience Cloud ID generated in Mozilla Firefox Browser

[ashokkumarm]

Hi All,

We have noticed, Visitor ID tracking gap with Mozilla Firefox Browser (Issue not persist in Chrome). Results in tracking gap of Visitor Journey.

Issue: Each screen load (PageView Call) getting different Experience Cloud ID in Single Page Application. And this issue only happen in Mozilla Firefox browser.

On further checking, we gets NS_BINDING_ABORTED error in network tab.

Note: This is Post-Login SPA, hence we used self-hosted (extracted from Adobe Launch) method.

Can any one explain,

1. why this only happen in Mozilla Firefox?

2. Is there any Adobe Analytics implementation gap?

3. If it is implementation gap, how to fix this?

Thanks and Regards
Ashok

[Jennifer_Dungan]

Hi,

Would you be willing to share a URL with me (via direct messaging so that it's not publicly posted here in this thread) so that I can take a look... both at which specific calls are being aborted, and so I can dig into the cookies to try and see what is happening?

I do not have an SPA, and I do not have the issue your are experiencing in Firefox.. I suspect there is something in your implementation that might be causing this... particularly since on an SPA, the Analytics and Visitor ID service should only be loaded on the initial page load (as subsequent pages should just have the content changed using JS... the resources and cookies should already be set and not change). So there's definitely something strange happening.... 

[ashokkumarm]

Hi @Jennifer_Dungan 

Thanks for your reply. As this banking sector, we are unable to share the URL & credential.

For your further information, We are getting NS_BINDING_ABORTED error in Mozilla Firefox. Which causes this issue. Is this anything related to Tracking Prevention. If No, how to resolve this NS_BINDING_ABORTED error.

Note: As mentioned earlier, this issue only occurred in Mozilla Firefox browser.

Regards

Ashok

[Jennifer_Dungan]

Fair enough... but the NS_BINDING _ABORTED could be caused by many different causes... so without seeing it, it will be very hard to diagnose...

This could be due to a timing issue, where the call starts, then is cancelled as another page load is triggered... This may not relate to your issue with multiple ECIDs at all, it may be an unrelated issue...

Is your site actually setting a s_ecid cookie? I was helping someone else recently (where they also had issue with different ECIDs between the main site and the checkout), and in their implementation, the ECID cookie wasn't being set....  in fact, neither was the backup s_vid or s_fid cookies.... 

The ECID works by the system checking for existing user Identifications, if found the ECID should be set according to the identified user... if nothing found, an ECID will be generated....  check to see if your site is properly setting any of these key user identifiers, otherwise, the ECID may be generated on each page view because it has no way to recognize the user.