Passing an ECID between App Measurement to the Web SDK pages and vice versa | Community
Skip to main content
D
DataNord
New Member
October 31, 2025
Solved

Passing an ECID between App Measurement to the Web SDK pages and vice versa

  • October 31, 2025
  • 2 replies
  • 325 views

Hello, We are working with one of our clients to implement analytics tracking on the site they own but they will use the same domain as us (lets take ".adobe.com" for example). Below are the examples of how our main site and the client site will technically look:

www.adobe.com

www.client.adobe.com

Basically, it will be a sub domain of our site. However, they can only implement tracking events using App Measurement Javascript implementation due to several reasons, while our main site runs on Adobe Web SDK.

 

Our goal is to maintain a single ECID across both our main site (runs on Web SDK) and the client site (App Measurement JS), so user journeys can be analyzed end-to-end in Analytics.

 

Note: Both will share same Org ID and TrackingServer (Edge Domain in this case).

 

What I’ve learned so far:

• Web SDK creates and stores its ECID on the Edge Network and saves it client-side in the kndctr__identity cookie.

• AppMeasurement / ECID Service stores its ECID client-side in the AMCV_@AdobeOrg cookie.

• These two cookies are not automatically synchronized, even if they share the same .airmiles.ca domain.

 

This means,

• A user starting on our main site (Web SDK) and then navigating to the client subdomain (AppMeasurement) receives a new ECID.

• A user starting on the client subdomain and later visiting the main site also gets a new ECID.

As a result, we will have same visitor > two ECIDs > fragmented journey data.

 

Questions:

  1. How do we make sure both of these implementations use same ECID when user navigates between these two sites ?
  2. I noticed that the App Measurement and Web SDK uses two different methods to append/pass ECID. Do we need a set up like below ?
    1. From www.airmiles.ca to www.test.airmiles.ca (Web SDK to App Measurement) - https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/commands/appendidentitytourl
      1. Will this only work if both sub domains run on Web SDK ?
    2. From www.test.airmiles.ca to www.airmiles.ca ( App Measurement to Web SDK) - https://experienceleague.adobe.com/en/docs/id-service/using/id-service-api/methods/appendvisitorid

Appreciate any leads on this!

Thanks!

Best answer by Jennifer_Dungan

I'm having trouble finding the documentation that they brought out around the time that WebSDK was released, but I do remember some of what it talked about.

 

You have to make sure you are using the "Migrate ECID from VisitorAPI to the Web SDK".. this will ensure that the ECID is set in a cookie, that should line up with the remaining sites on AppMeasurement.

 

I believe so long as you are running both, you will need to ensure that cookies are being set.

 

You can also use the AppendVisitorID function to pass the ECID between sites, and make sure that the passed value is the one used to identify the user... 

2 replies

D
DataNordAuthor
New Member
October 31, 2025

I forgot to mention a note that the third party cookies (demdex) are disabled on Web SDK  due to privacy concerns.

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
November 1, 2025

I'm having trouble finding the documentation that they brought out around the time that WebSDK was released, but I do remember some of what it talked about.

 

You have to make sure you are using the "Migrate ECID from VisitorAPI to the Web SDK".. this will ensure that the ECID is set in a cookie, that should line up with the remaining sites on AppMeasurement.

 

I believe so long as you are running both, you will need to ensure that cookies are being set.

 

You can also use the AppendVisitorID function to pass the ECID between sites, and make sure that the passed value is the one used to identify the user... 

    bjoern__koth
    Community Advisor and Adobe Champion
    bjoern__kothCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    November 1, 2025

    In addition to the AppendVisitorID function on pages with Visitor ID Service, in Web SDK terms this would be appendIdentityToUrl, but it would have to be tested if that works reliably.

    https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/commands/appendidentitytourl

    Cheers from Switzerland!
      Terms & ConditionsAccessibility statement

      Loading footer...