Hi there,
What are some of the ways an ECID would be deleted from an identityMap for an existing customer? I originally thought setting the ExperienceEvent TTL on our web/app dataset would help remove older ECIDs outside of the time window, but was told this is not the case.
Then I wonder, for customers with older ECIDs that we want to remove, or we if we just want identityMap to show most recent ECIDs within x days, how is that possible?
Thanks.
Solved! Go to Solution.
Hi @akwankl,
Yes, that's correct. In addition, if you want to prevent the stitching of the profile because of shared devices, please refer to the FPID solution mentioned below:
https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/identity/first-party-device-i...
Note: For edge cases, it may not be necessary to over-engineer the solution. If it is a measurable percentage of your traffic, you can think of other solutions.
Regards,
Kumar Saurabh
Hi @akwankl,
The ECID will get deleted automatically when the below situation occurs:
When a graph with 50 linked identities (including ECID) is updated, Identity Service will apply a “first-in, first-out” mechanism and delete the oldest identity to make space for the newest identity for this graph.
Deletion is based on identity type and timestamp. The deletion priority is as follows:
Cookie ID (ECID in your case)
Device ID
Cross-Device ID, Email, and Phone
Documentation- https://experienceleague.adobe.com/en/docs/experience-platform/identity/guardrails
Regards,
Kumar Saurabh
Thanks @Kumar_Saurabh_ ,
So if two profiles are mistakenly stitched together by a single ECID (the ECID logging into multiple accounts), the only way to "unstitch" that profile would be to delete the ECID through data lifecycle API so that the identityMap would separate?
Thanks.
Hi @akwankl,
Yes, that's correct. In addition, if you want to prevent the stitching of the profile because of shared devices, please refer to the FPID solution mentioned below:
https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/identity/first-party-device-i...
Note: For edge cases, it may not be necessary to over-engineer the solution. If it is a measurable percentage of your traffic, you can think of other solutions.
Regards,
Kumar Saurabh
Views
Likes
Replies
Views
Likes
Replies