Solved
Migrating legacy AAM to WEBSDK with launch
What is impact of migrating legacy AAM to WEBSDK with launch on existing Data? What changes we need to do in terms of traits and signals in AAM?
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
The biggest impact to traits is that you have to change the expression criteria to match Web SDK data. I'm going to assume you're currently using Server-side forwarding from Analytics. The big change with Web SDK is that the data goes from Edge directly to AAM without going through Analytics first. As such, your trait expressions will go from looking for props, evars, and events to XDM values. Typically, we would add OR criteria to your existing trait expressions so that if you have pages still using SSF, the traits will still work with Web SDK or SSF data.
I'm not sure how urgent the move is, but there are plans for making the transition/migration from SSF to Web SDK for AAM easier so that you don't have to manually update X number of traits. If you can wait a few quarters, you may find a much faster migration path. I can't commit to timelines on a post like this or even if these initial plans are going to pan out. We just know how big a move it is, and we are planning to make it easier than it is now.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.