Hi Adobe Community,
I have a question about a rise in ECIDs in my platform. So in my platform, we have ECIDs (device identifiers) that are created whenever a customer performs traffic on one of our tagged websites. Now, we can identify/verify these ECIDs when a customer logs into their account from that ECID - so when a customer goes onto our site and logs into their account, we get a hashed ECN which is then stitched to the ECID on its Adobe profile. So if a customer then went online again from that same device, we would already know their profile bc they had logged on etc etc. Now, we do have another type of profile that we call a pseudonymous profile. This is an ECID that we don't have a hashed ECN for. So, a customer that never logged into their account from their device or maybe a customer that is using a private browser or cleared their cookies etc etc. So, we purge any pseudonymous profiles that have been inactive in our platform for 30+ days as a part of our profile cleanup. So, typically the number of pseudonymous profiles in our platform stays pretty steady. However, recently we have noticed that the number of pseudonymous profiles in our platform has been steadily increasing which has been increasing the number of ECIDs in our platform. Any ideas why that is?
Thanks,
Nick
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi, @NickMannion,
Do you use Web SDK for your data ingestion? If so, check your Privacy settings and the consents. Make sure to configure the Privacy to Pending, this way you have more control on profile creation as you can choose which profiles to create or not, i.e. you don´t need profiles with denied cookies.
Recently, Adobe changed its native setConsent functionality so now, as it creates profiles either if the consent were denied or accepted, thus it sends much more ECIDs.
Do a fast query to check how many profiles you have with negative cookies, that might give you a hint.
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
I would use the profile snapshot dataset:
profile_snapshot_export_<your dataset id>. Look for it in your datasets UI. If there are several of these, make sure to select the one that, in sdescription, has the following: "Default timebased merge policy profile export".
Identify the field you are mapping for your cookie policies. If you used Adobe Standart Consent 2.0, you are probably looking for something like this path:
For example, consents.marketing.any.val = 'n'.
Then, select the timestamp you are looking for. I would use timestamp::date > '2025-03-24' for example.
Views
Replies
Total Likes