Expand my Community achievements bar.

Record is not present in profile store

Avatar

Level 1

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.

 

 

4 Replies

Avatar

Level 4

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

 

Hi Sakthivel,

 

In my use case only, particular attribute is missing for one profile.

 

For Example :

 

lets take few attributes 1)Email 2)coupon code 3)offer code.

 

1)For one profile : test1@gmail,com in profile store above all attributes are coming

2) test2@gmail.com in profile store i see offer code attribute is missing rest all are appear.

 

How it is that possible. Whereas i am able to see in datalake.

 

This is possible even when the profile exists and other attributes are present.

When only one attribute is missing for a specific profile, the most common reasons are:

If the same profile exists in multiple datasets, Profile applies the merge policy.
If another dataset has a more recent record for that profile where offer code is null or not populated, Profile will pick that record and the attribute will appear missing — even though it exists in the Data Lake.

Attribute was ingested as null in a later event/batch
Profile supports partial updates. If a later ingestion for the same profile does not contain offerCode (or sends it as null), that value can be cleared in the unified profile, while other attributes remain.

Attribute-level data did not qualify for Profile ingestion
Even when identity is valid, Profile ingests attributes independently. If the field mapping, data type, or value validation fails for that attribute in a specific record, only that attribute is skipped — not the whole profile.

Avatar

Level 7

@sesha_saicharanMa the most likely explanation is,

  • Data precedence you might have set in the Merge Policy
    • When multiple profile-enabled datasets populate the same attribute, the merge policy decides which dataset wins. If the higher-priority dataset if you have set custom data precedence order has that field empty or null, the profile will show it as missing, even though another dataset still has a value.
  • Attribute value getting overwritten by a Null value from a different dataset for the same profile:
    Same as above for a default merge policy (which is set to show most recent records) If two datasets write to the same XDM field and the later ingested record carries that field as null, AEP shows the most recent value for that attribute which is null. The value still exists in the original dataset table, but the profile reflects the latest update.