Thank you for replying. I am aware of the Experience Cloud Debugger, and I use it indeed to verify which activities I qualified for when debugging.
For tracking however, I require that list of activities somewhere in JS code. Something like the ttMeta plugin used to provide.
When I follow the steps on the Response Tokens page in the section "Debugging (similar to the ttMeta plugin)", this works for XT tests and for all A/B test experiences where the page is modified.
When an experience has no modifications (because it is the control experience), I cannot see them in the response tokens.
FYI: Target is loaded by Launch, but that should not really matter here. Currently v2.1.0 is used, but the same behaviour was observed in earlier versions.