Moved to Web SDK on our website - do not see any traits in AAM | Community
Skip to main content
Level 3
January 30, 2024
Question

Moved to Web SDK on our website - do not see any traits in AAM

  • January 30, 2024
  • 1 reply
  • 2058 views

 

We do not yet have our AAM synch call set up and we are still doing server-side forwarding.  We do have the right AAM Org ID set up within our Launch Web SDK.  This particular trait was set up after we moved to the WebSDK. It is fed from website traffic.  Is the problem that WebSDK uses the ECID rather than the MCVISID?  Notice that the Total Trait population in the graph shows that there are a little over 30K in the total traits but those numbers do not show up in the 1 Day: thru 90 day legend below.  How do we get this working properly?

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

1 reply

Tof_Jossic
Adobe Employee
Adobe Employee
February 6, 2024

@valerie_anders Can you please raise a Support ticket with us so we can take a look at the AAM instance as well as your web property?

Level 3
March 11, 2024

Thank you.  We worked with Customer Support.  We added AAM as a service to our WebSDK datastream.  We followed the steps outlined in this tutorial.  https://experienceleague.adobe.com/docs/platform-learn/implement-web-sdk/applications-setup/setup-audience-manager.html?lang=en and we see the traits populating.

Tof_Jossic
Adobe Employee
Adobe Employee
March 12, 2024

@valerie_anders Thanks for taking the time to confirm, glad you are up and running with this 🙂