In Adobe Experience Platform, even if your web event dataset is profile-enabled with ECID (Experience Cloud ID) as the identity field, the records associated with those ECIDs will still appear in the Customer Profile store. This is because AEP’s Identity Service links experience event identities like ECID (commonly from Web SDK or Adobe Analytics) with profile records, even if corresponding record class datasets (Person, Account) do not have ECID explicitly present.
Key points are:
ECID is a primary and shared identity namespace used to associate web events with profiles.
Identity Service links profiles via matching identity namespaces and values (like ECID, email, CRMID).
Profiles from CRM or record class datasets without ECID can still get linked in the identity graph to profiles having ECIDs if other common identities exist.
Web event data ingested with ECIDs will generate or update profiles in the Customer Profile store, even if the Person or Account datasets lack ECID.
Identity linking unifies data across multiple datasets based on common identifiers for a holistic customer profile.
Therefore, whenever ECID is captured in the web event dataset, those records will be visible in the Customer Profile store due to the linking behavior of the Identity Service, regardless of ECID presence in other profile datasets
