InApp with no ECID Identity

[Silvio6]

Hi, we are actually working on the inApp messages for our implementation. We have ECID and an internal id both selected as identities.

The internal id is getting send through an event (into the identity map) and stored in the AEP profile into the identity map too.

The problem is that when we want to create an inApp campaign, using the internal id as identity instead of ECID, my profile gets excluded with an exclusion message based on missing namespace. For sending the internal id we only embed the identity map object into the xdm (it seem to be working as we can see the value getting stord into identityMap.identities.0.internal_id, but I think we should be applying the updateIdentities() API , for having it properly added to the profile as identity, is it correct?

[Pankaj1390]

Hi @Silvio6 ,

The issue you're encountering with AJO in-app messaging stems from how your internal ID is being handled within the ECID framework. While you're seeing the internal ID stored in identityMap.identities.0.internal_id, simply storing it isn't sufficient for AJO to recognise it as a valid identity for targeting. AJO relies on the updateIdentities() API call to properly register and update identities within the AEP profile.

Therefore, your suspicion is correct: you should be using the updateIdentities() API. Storing the ID in the identity map alone doesn't trigger the necessary profile updates for AJO targeting. This API explicitly informs AEP to treat the internal ID as a first-class identity, allowing AJO to use it for campaign targeting.

Here's a breakdown of why this is happening and how to fix it:

• Identity Resolution: AJO uses the ECID as its primary identifier. When you use a different identity (like your internal ID), AJO needs to resolve it to the ECID to link the profile. The  updateIdentities() API facilitates this resolution process. Without it, AJO doesn't recognise the internal ID as a valid identifier linked to a profile.

• Namespace: The "missing namespace" error indicates that AJO cannot find the internal ID within the recognised identity namespace. The  updateIdentities() API call allows you to specify the namespace associated with your internal ID, resolving this issue.

• Implementation: You need to modify your event implementation to include a call to  updateIdentities(), passing your internal ID along with its associated namespace.

Thanks,

Pankaj