Impact of not using ECID extension in AEP WebSDK | Community
Skip to main content
K
Kaushik_Ganguly
Level 2
April 11, 2025
Solved

Impact of not using ECID extension in AEP WebSDK

  • April 11, 2025
  • 1 reply
  • 728 views

Hi,
We are migrating from Adobe Analytics to AEP Web SDK. We are not using the ECID extension; instead, we are using the custom code below in a rule to capture the ECID and send it to Analytics Workspace:

return alloy("getIdentity")
.then(function(result) {
_satellite.setVar("experienceCloudID", result.identity.ECID);
});

This is working fine. However, when we were using Adobe Analytics with the ECID extension, we used to see two additional server requests—one from Adobe Audience Manager (type: ID Sync) and the other from Adobe Experience Cloud (type: Other). Since we no longer see these in the AEP Web SDK implementation, we wanted to understand the potential impact and whether any additional configuration is needed to ensure we are not missing any important data.

Thanks,

Kaushik Ganguly

Best answer by bjoern__koth

Hi @kaushik_ganguly 

the Web SDK is effectively replacing the legacy libraries and some network calls may no longer happen or happen behind the scenes, server-side. Adobe has built up AEP as a new architecture that orchestrates everything. So disappearing calls are actually a good thing.

 

About your ECID getIdentity call: do you need this information on the client-side? Just mentioning since this is asynchronous and may lead to timing problems should your analytics calls fire earlier. So, should you not need this for other systems, you could automatically map this information in the datastream mapping configuration and hence circumvent the asynchronous timing problems. This is possible because the ECID is automatically added in every Web SDK call anyway.

 

Find more information here: 

https://experienceleague.adobe.com/en/docs/experience-platform/tags/extensions/client/web-sdk/accessing-the-ecid

 

(-> "preferred method")

1 reply

bjoern__koth
Community Advisor and Adobe Champion
bjoern__kothCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
April 12, 2025

Hi @kaushik_ganguly 

the Web SDK is effectively replacing the legacy libraries and some network calls may no longer happen or happen behind the scenes, server-side. Adobe has built up AEP as a new architecture that orchestrates everything. So disappearing calls are actually a good thing.

 

About your ECID getIdentity call: do you need this information on the client-side? Just mentioning since this is asynchronous and may lead to timing problems should your analytics calls fire earlier. So, should you not need this for other systems, you could automatically map this information in the datastream mapping configuration and hence circumvent the asynchronous timing problems. This is possible because the ECID is automatically added in every Web SDK call anyway.

 

Find more information here: 

https://experienceleague.adobe.com/en/docs/experience-platform/tags/extensions/client/web-sdk/accessing-the-ecid

 

(-> "preferred method")

Cheers from Switzerland!
    K
    Kaushik_GangulyAuthor
    Level 2
    April 14, 2025

    Hi @bjoern__koth , 

    Thanks for your response. If we map the ECID in the DataStream but don't use the ECID extension, we won't get those Audience Manager calls. Could you help me understand what those above Audience Manager calls do, and if we aren't getting them in the AEP Web SDK, aren't we missing some important data?

     

    Thanks,

    Kaushik Ganguly

    bjoern__koth
    Community Advisor and Adobe Champion
    bjoern__kothCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    April 14, 2025

    Hi @kaushik_ganguly 

    if you configure the datastream and add your services to it, these client-side calls should all be handled in the Experience Platform itself (to my knowledge)

    Cheers from Switzerland!
      Terms & ConditionsAccessibility statement

      Loading footer...