I'll take a step back to approach the question.
We are moving to WebSDK from at.js. While testing I see that the QA link returns the experience. But if I switch the QA link to audience mode, then nothing gets returned - the audience has a condition that checks certain profile attribute value, and the correct value is being passed from the client through events[0].data.__adobe.target object.
It would help me to see what response tokens are returned for this user, but I’ve never seen them in the responses for some reason ... so then there's one more option - switch Target to debug mode and generate debugging token in Target UI. But the token generated in the Adobe Target interface no longer works because alloy.js doesn't accept mboxTrace parameter.
I know about an alternative way to view logs - to authorize in the extension, go to Logs > Edge, and create a debugging session, but I wasn’t able to find anything useful in those logs similar to what mboxTrace was returning - all existing profile attributes of a user. Switching "Target Trace" option in the extension also doesn't work, because no at.js library is present.
I am mistaken somewhere ? What is the best approach to debug Adobe Target requests in WebSDK ?
