Record is not present in profile store

[sesha_saicharanMa]

Hi,

For one of my use case i have observed that for one of the profile one attribute is missing in Profile snapshot table but it is present in Dataset table. 

what is the root cause for that, where can i find that. and what are the resolution steps if any.

Thanks, waiting for your response.

[Karuppiah_Sakthivel]

Hi Sesha,

This happens when the record is stored in the Data Lake but never makes it into the Profile Store. A few common causes:

1. Missing or invalid identity value – Profile only ingests records that contain a valid primary identity. If the identity is null, the attribute will appear in the dataset but not in Profile.
2. Batch profile processing delay – Batch data can take several hours to populate the Profile Store after ingestion. While Adobe does not give an exact SLA, real-world behavior is typically 3–8 hours, and in heavy-volume scenarios it can take longer (up to ~24 hours).
3. Merge policy – If another dataset has a newer value, merge policy may override and hide this attribute.
4. Field not part of a profile-enabled field group – If the XDM field isn’t enabled for Profile, the value is ignored by the Profile pipeline.

Streaming ingestion

Profile updates happen near real-time (typically within seconds).
This is because streaming data goes directly into the Profile pipeline as it arrives.

Batch ingestion
Batch data goes to the Data Lake first, and then Profile processes it through a separate internal pipeline. This Profile pipeline cannot be triggered manually and can take several hours depending on volume.

Adobe explains how Profile decides what data is included here:

https://experienceleague.adobe.com/en/docs/experience-platform/profile/home