AAM Updates

Issue in ./help/tutorial-web-sdk/setup-audience-manager.md

Overall:

This section presents an opportunity to explain how AAM Cross-Device Data sources relate to AEP UIS namespaces. Since customers will likely only be doing this AAM setup if they are AAM customers, we can get a bit AAM specific. Going back to some comments around setting up identity namespace in the initial configuration setting, perhaps we have a step there that redirects them to the AAM section if they are AAM customers to set up an AAM cross-device data source. With that context, here is my feedback on this page:

1. Instead of setting up a new standard, cookie data source, I would recommend we have them setup a new, Cross-Device data source that they can then see shows up in the AEP UIS interface. Either that or reference an existing Cross-device data source that they would have already been using in AAM.
2. When creating the trait, just after you enter the expression (step 9), it's critical that you click the blue "Add Rule" button. If you just click "Save" as instructed in step 10, the rule will save, but without the expression.
3. When creating the segment, it looks like Step 5 has the next step listed in the same step, only it has a 1. before it. Probably a funny formatting issue with the bullets. But on that note, there's really no need to create an integration code for this segment, so you can probably just do away with that sentence/instruction altogether and fix it so step 5 is setting the data source for the segment.
4. This one is probably splitting hairs a little bit, but step 10 when creating the destination should read "Select the Luma domain" instead of "your domain."
5. Going back to the concept of expanding on how identity names spaces and AAM Cross-Device data sources are connected, an additional validation step would be to login and then send in a few hits. Then, when the learner reviews the data in AAM, they can see that the trait was stored both on the device level AND on profile level. One of the most common questions we get in support is how to maintain the same customer ID sync they had before Web SDK into their new SDK deployment. This additional validation step would show how the identity in the Identity Map of Web SDK maps over to the AAM side and maintain that legacy ID sync. There are also several notes we'd want to make here about why happens when the Identity namespace and AAM integration code are different and which to use.

Update ./help/tutorial-web-sdk/setup-audience-manager.md, starting by reviewing the existing AAM setup steps and their formatting. Incorporate the Cross-Device data source and AEP UIS context, correct the trait and segment instructions, change the destination wording to "Luma domain," and add the proposed identity validation and explanatory notes; done means all five feedback areas are addressed in the tutorial.

Written by the indexing model from the issue text.