Expand my Community achievements bar.

Help shape the future of AI assistance by participating in this quick card sorting activity. Your input will help create a more effective system that better serves your needs and those of your colleagues.
SOLVED

ECID stitching taking time

Avatar

Level 4

Hello,

 

We are trying to share an experience with user while he logsin to the website.

However, we tried testing with test profiles and next day if we login with new browser (new ECID) it takes around 5-10 mins for the experience we created in adobe target to reflect.

This is not a qualification issue, as profile is already qualified for the segment and is present as existing profiles for that segment.

Is there any documentation from Adobe supporting the fact that it sometimes it takes new ECID to stitch with profile_ID even though it works on real time

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Hi @ShivaniM ,

Is this a Web SDK implementation? And are you sharing Platform segments to Adobe Target? It can take around 5-10 min for the identity graph to incorporate the new ECID and then be able to start using the edge profile and segments in Target. One way to improve the performance of this is to switch to using the authenticated identity as the primary identity when users log in. This way, the profile will be looked up using the authenticated id instead of the ECID--it should be immediately accessible without having to wait for the new ECID to graph.

We are now recommending this as a best practice in our Web SDK tutorial: 

dwright_0-1700590464865.png

https://experienceleague.adobe.com/docs/platform-learn/implement-web-sdk/tags-configuration/create-d...

View solution in original post

1 Reply

Avatar

Correct answer by
Employee Advisor

Hi @ShivaniM ,

Is this a Web SDK implementation? And are you sharing Platform segments to Adobe Target? It can take around 5-10 min for the identity graph to incorporate the new ECID and then be able to start using the edge profile and segments in Target. One way to improve the performance of this is to switch to using the authenticated identity as the primary identity when users log in. This way, the profile will be looked up using the authenticated id instead of the ECID--it should be immediately accessible without having to wait for the new ECID to graph.

We are now recommending this as a best practice in our Web SDK tutorial: 

dwright_0-1700590464865.png

https://experienceleague.adobe.com/docs/platform-learn/implement-web-sdk/tags-configuration/create-d...