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
Solved! Go to Solution.
Views
Replies
Total Likes
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:
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:
Views
Likes
Replies
Views
Likes
Replies