1. Depending on the amount of data you pass in, the Signal search tool (https://experienceleague.adobe.com/docs/audience-manager/user-guide/features/data-explorer/signals-s...) would be an excellent place to start. Just note it is sampled, so you may not see everything you pass in. That said, if you filter for anything with web.webPageDetails, you would probably find something. If you haven't seen this tutorial yet, I highly recommend it: https://experienceleague.adobe.com/docs/platform-learn/implement-web-sdk/overview.html?lang=en. If you expand the Applications Setup and Audience manager section, you'll see details on how to create a trait for Web SDK data.
2. You can't use the same integration code for multiple traits, so if you're cloning traits, you'd need to adjust the integration code for each trait. Having said that, I'm not sure why you'd need an integration code for traits like this anyway, so depending on your scenario, I'd question the need even to have an integration code.
3. It's real-time, but like all AAM reports, you won't see the results until the next day when the UI reports update. If you have a cookie-based destination that you use for validation, then that would show the immediate results as well. That said, remember that there's at least an hour wait for settings in the UI to be pushed to the edge. I recommend waiting 4 hours to be sure.
4. Either. It really depends on how your AAM instance is organized per your business needs. I'd be hard-pressed to offer a hard and fast rule with only this community post as my background of your implementation. By and large, though, data sources are usually classified as things like websites, mobile apps, or onboarded data. How the data is passed (Analytics or Web SDK) is less important. then where the data comes from. So unless you have a compelling reason to switch data sources (again, my background is limited), I'd think you'd just want to keep the same one.
