Skip to main content
Shubham_AEP
Shubham_AEP
Level 2
Mar 5, 2026 1:24 PM UTC
Question

Profile not updated from Experience Event — Identity path issue?

Hi AEP Community,

I’m doing a POC, ingesting Experience Event data and Individual Profile data, into Adobe Experience Platform and I’m seeing this behavior:

  • Data Lake ingestion works (5 records appear)

  • Real-Time Customer Profile shows 0 records / 0 identity matches

Here’s my setup: (Please note all are dummy data).

Sample Dummy Profile Schema Payload:

{
  "_object": {
    "StCd": "CA",
    "CNUM": "1125"
  },
  "_id": "/uri-reference",
  "personID": "Sample value"
}

  • Primary Identity: CNUM

  • Namespace: CNUM

Sample Dummy Event Schema Payload:

{
  "_object": {
    "EnEvenObj": {
      "CNUM": "1125",
      "Type": "Dep",
      "EventDate": "2026-02-20T20:20:39+00:00"
    }
  },
  "eventType": "adve.comp",
  "timestamp": "2026-02-20T20:20:39+00:00",
  "identityMap": {
    "key": [
      {
        "id": "Sample value",
        "authenticatedState": "ambiguous",
        "primary": false
      }
    ]
  }
}

Observations:

  • Namespace and Primary Identity are defined in both schemas

  • Data was ingested after Profile was enabled

  • Monitoring shows Data Lake = 5, Profile / Identity = 0

Question:

Does the identity field path mismatch between the Profile schema (_object.CNUM) and the Event schema (_object.EnEvenObj.CNUM) explain why the events are not attaching to the Profile?
Or is there something else in the payload (e.g., identityMap) preventing Profile stitching?

Has anyone seen this exact behavior, and what’s the recommended approach — flatten the identity path in the Event payload, or use a proper identityMap?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

bjoern-koth
Adobe Employee
bjoern-kothAdobe Employee
Adobe Employee
Mar 6, 2026 11:51 AM UTC

Hi ​@Shubham_AEP 

have you created a custom identityNamespace called “key”, since that is what you are sending with the WebSDK call?

Try the following

  • Identity Namespaces: create a custom identity namespace
  • Profile schema
    • create a dedicated field of type string to contain your identity
    • mark that field as primary identity and choose the identityNamespace you just created
  • ExperienceEvent / Web SDK: make sure to use that same identityNamespace in your WebSDK call’s identityMap instead of the “key”

 


 

Translate
Cheers from Switzerland!
    SG14_97
    SG14_97
    Level 3
    Mar 10, 2026 11:57 AM UTC

    hi ​@Shubham_AEP ,

    identityMap is different concept which is useful when you have systems with variable identities at any given point coming into AEP. That being said it doesn’t matter if you have a primary key at attribute level and ingesting secondary identifiers at the identityMap level at the end AEP merges all fragments with the same value in a given identity namespace.

    Few things to check :
    a.Both your event and profile schema are pointing to the same namespace?

    b.When you say 5 records visible in datalake (what are referring the event ingestions or 5 dummy profiles?)
    c.The profile ingestion you have done is via streaming or via any batched connector?​​​​​​​​​​​​​​

    ​​​​​​​d.In the monitoring tab you can see whether identity resolution is failing or do you see any errors?

    e.Are your datasets profile enabled (could be your schema is enabled but datasets are not).

    ​​​​​​​f.Make sure from your namespace tab (profiles section), you are using correct namespace to ingest via api.

     

    Regards,

    Sayantan

    Translate
      Sukrity_Wadhwa
      Sukrity_Wadhwa
      Level 4
      Mar 16, 2026 9:27 AM UTC

      Hi ​@Shubham_AEP,

      Were you able to resolve this query with the help of the provided solutions, or do you still need further assistance? Please let us know. If any of the answers were helpful in moving you closer to a resolution, even partially, we encourage you to mark the one that helped the most as the 'Best Answer'.

      Thank you!

      Translate
      Sukrity Wadhwa
      Terms & ConditionsAccessibility statement

      Loading footer...