Web SDK - Intetity Map - is there any way to preview?

​@Michael_Soprano Unfortunately no, there is no direct way. Use Debugger/Assurance for the sent identityMap, and Target Traces for the resulting Target profile evaluation.

It will show

Matched activities
Unmatched activities
Request details
Profile snapshot

Thanks,

Sarthak

To be precise, Target does not provide a full preview of Web SDK identityMap in the UI or via standard Target APIs. 

With Web SDK, identities are sent in XDM to Platform Edge, and Target uses the relevant IDs for profile resolution, but the full identity graph remains an AEP/Edge concern rather than a Target-visible object. If you need to inspect what identities were sent, use Experience Platform Debugger or Assurance. If you need to validate identity stitching across devices, use the AEP Identity Graph Viewer.

No, Adobe Target does not provide a UI or API to preview or retrieve the identityMap. The identityMap is part of the Adobe Experience Platform Identity Service and is sent as part of the AEP Web SDK (sendEvent) request. While Adobe Target uses these identities for personalization and visitor identification, it does not expose them through the Target interface or Target APIs.

To verify it, Adobe recommends inspecting the Web SDK sendEvent network request (or using Adobe Experience Platform Debugger) to view the identityMap in the request

Hey ​@Michael_Soprano  - I presume you open this discussion in relation to the related question you asked below -   Adobe Target destination | Community  

As mentioned by ​@Pankaj_Sabharwal ​@SarthakBh - all points correct. 

As far as I know - Target profile typically expose Target-related identifiers and profile data, but not the full identityMap received by Edge.  

If you're looking to validate which identities are being sent, I'd recommend:

• Adobe Assurance: This is probably the best option. You can inspect the Edge requests and verify the identities being processed by the Edge Network.
• Browser Network Calls: If your implementation explicitly sends identities in the sendEvent payload, you can inspect the Web SDK request and confirm the values being passed. 
• AEP Identity Graph / Profile Viewer: If the data is profile-enabled, you can verify whether identities are being stitched correctly and linked to the expected profile. 

One thing worth noting is that some identities, such as the ECID, are added and processed by Edge and may not be directly visible in the request payload itself.

Hope this helps. Thank you.