Does profile-id value changes in any circumstances

[Pradeep-Jaiswal]

Once data is ingested into dataLake, it create a profile in profile store. when we query the profile using ECID or other namespace, we do see unique profile-id associated with the record. now does this profile-id changes under any circumstance for that particular profile ? if yes, what are those scenario ?

is this profile-id present in any dataset, if we need to query it using queryService ?

[Imbalakumar]

Hi @Pradeep-Jaiswal 

Profile ID is a unique, auto-generated identifier associated with a customer profile. It acts as a key identifier, ensuring all data points are correctly linked to the appropriate profile.

it ensures that all data points, regardless of their source (web analytics, CRM, etc.), are correctly associated with the right customer profile.

Yes, the Profile ID is available within Adobe Experience Platform datasets, while it's used for internal data management and can be seen as an attribute, it's not directly mapped to destinations as a regular attribute. 

Refer this for more details - https://experienceleague.adobe.com/en/docs/experience-platform/dashboards/guides/profiles

Thanks,

Bala

[Pradeep-Jaiswal]

But the Q is Does profile-id value changes in any circumstances ?

[Imbalakumar]

Hi @Pradeep-Jaiswal 

Profile ID wont change, it may be deleted while you remove some profile.

This is auto-generated identifier associated with a customer profile, it will remain same and that profile keep getting the enrichments.

Profile ID is not a dynamic value that will change while a new attributes value added to that profile.

[KaruppaiahRa1 · Accepted solution]

The Profile ID keeps getting generated for the same customer based on some backend logic. As a result, a single customer ends up with multiple Profile IDs.

For example, here are some of the Profile IDs generated for me:

• Profile ID: GyAeHQFCb5INEX1LFkPiruvPPAtnXAg

• Profile ID: G9w2SAFBZoUFnbCzpwI

• Profile ID: GwweHQFBZINjxSUX

This pattern continues, creating several different Profile IDs—even though the ECID and Customer ID remain the same across records. I feel, it is creating based on different Dataset.