We are unable to see any Real-Time Customer Profile created in the Profile UI, even though:
Data is successfully ingested
Data is visible in Dataset Preview
Schema and dataset are profile-enabled
Primary People Identifier is provided
identityMap is included in the payload
Profiles are not visible even after 3+ days.
payload -
"body": {
"xdmMeta": {
"schemaRef": {
"id": "https://ns.adobe.com/acssandboxgdcone/schemas/dasd3e931dddf9b4d83f43d606d9a1b137b70b1946e1ead2",
"contentType": "application/vnd.adobe.xed-full+json;version=1.0"
}
},
"xdmEntity": {
"_rumaStoreSite": {
"identityMap": {
"loyaltyMembershipNumber": [
{
"authenticatedState": "ambiguous",
"id": "1006",
"primary": true
}
]
},
"rumaStore": {
"identities": {
"loyaltyMembershipNumber": "1006",
"email": "test+05@gmail.com"
},
"rumaStoreMemberProfile": {
"email": "test+05@gmail.com"
"firstname": "lorum",
"gender": "Male",
"lastname": "Ipsun",
"loyaltyMembershipNumber": "1006",
"title": "Mr."
}
}
},
"_id": "/uri-reference",
"_repo": {
"createDate": "{{currentTime}}",
"modifyDate": "{{currentTime}}"
},
"timestamp": "{{currentTime}}"
}
}Is there any additional config I should do ?
Views
Replies
Total Likes
Hi,
Have you created Data Stream by selecting the newly created profile schema with Adobe Experience Platform Service?
While I faced he same issue for the first time, I saw the profile and identity map getting created after creating a datastream.
Datastream configuration documentation:- https://experienceleague.adobe.com/en/docs/experience-platform/datastreams/configure
Views
Replies
Total Likes
Thanks for your response.
My understanding is that a Data Stream is required only for Web SDK or Mobile SDK integrations. As a troubleshooting step, I created a Data Stream and mapped it to the same schema to check if it would resolve the issue. The profile is still not visible even after creating the Data Stream.
Views
Replies
Total Likes
Yes, Datastream is created to get collect the data from Web SDK, Mobile SDK and to use the data in edge segmentation, personalization destinations, etc.
In my case, it might be the latency and the coincidence, I saw the realtime profile and identityMap after creating the data stream for collecting event data through WebSDK.
When the schema and dataset is profile enabled, after a successful data ingestion real time profile must be created.
You have already did all those configurations.
Best of luck with your explorations!
Hi @Mario248
I think identity map in your payload is not in the root, that might be the reason, can you try to add the identity map in the root? like below
"xdmEntity": {
"_id": "<Unique record ID>",
"timestamp": "2025-12-30T10:00:00Z",
"identityMap": {
"loyaltyMembershipNumber": [
{
"id": "1006",
"authenticatedState": "authenticated",
"primary": true
}
]
},In Adobe Document , it is in the xdm meta , but it seems wrong , it should be in the xdm entity.
Hope you have created identity namespaces with the same symbol.
Hello @Mario248 ,
I believe your XDM class is Profile for this data schema.
I’m not sure if you’ve already tried this, but for data ingestion into the Profile class via API, the easiest way is to use the HTTP API. You don’t need to configure any data streams for this approach.
You can follow the steps outlined here:
Hope this helps!
Kind regards,
Parvesh
Hello @Mario248
To confirm are you attempting to ingest data into an XDM Individual Profile Class? The identityMap object is not an OOB mapping for the a schema with the class XDM Individual Profile.
It also appears you are missing a comma after
"email": "test+05@gmail.com"
I would try with the following payload
{
"body": {
"xdmMeta": {
"schemaRef": {
"id": "https://ns.adobe.com/acssandboxgdcone/schemas/dasd3e931dddf9b4d83f43d606d9a1b137b70b1946e1ead2",
"contentType": "application/vnd.adobe.xed-full+json;version=1.0"
}
},
"xdmEntity": {
"_rumaStoreSite": {
"rumaStore": {
"identities": {
"loyaltyMembershipNumber": "1006",
"email": "test+05@gmail.com"
},
"rumaStoreMemberProfile": {
"email": "test+05@gmail.com",
"firstname": "lorum",
"gender": "Male",
"lastname": "Ipsun",
"loyaltyMembershipNumber": "1006",
"title": "Mr."
}
}
}
}
}
}
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies