AEP Web SDK Authenticated States in AAM
Learn how to resolve the issue where cross-device IDs/data sources are not syncing or behaving in the same way as before you migrated.
Description description
Environment
- ÃÛ¶¹ÊÓƵ Experience Platform (AEP)
- ÃÛ¶¹ÊÓƵ Audience Manager (AAM)
- Recently migrated to AEP Web SDK
- AAM is enabled in the receiving datastream
Issue/Symptoms
You recently migrated to using the AEP Web SDK to pass data to AAM, and the cross-device IDs/data sources are not syncing or behaving in the same way they did before you migrated. For example, traits are no longer being stored against the cross-device profile.
Resolution resolution
The AEP Web SDK documentation shows the ambiguous authentication state in all the example code. If you copied that example, then that ambiguous authentication state is being passed to AAM as the unknown auth state. In this state, the ID sync is still performed, and the CRM ID is still linked to Experience Cloud ID, but expressed traits will not be stored against the authenticated profile. This is likely what is causing the issue.
To fix this issue, change the auth state to authenticated when users log into your property. Do not be concerned about what might happen to your AEP implementation if you change this state. AEP Web SDK only supports auth states for cases of running an AEP and AAM implementation together, and the authentication state needs to be passed to AAM. While the primary node in the identity map is meant for AEP, the authenticatedState node is there only for the sake of existing AAM implementations.
To learn more, refer to Identity data in the Platform Web SDK in the Web SDK Guide, as well as documentation on AAM authentication states. For more information on how AEP Identity Namespaces and AAM Cross-device data sources are related, see this How are AEP Identity Namespaces related to AAM Data Sources?Ìý²¹°ù³Ù¾±³¦±ô±ð.