A couple of different options:i) If your click element in Exp A & Exp B have the same unique ID/Class then you could update the auto-generated selectorii) You could implement trackEvent for the click tracking, via your tag manager or application code, and then use the "viewed mbox <somemboxname>" op...

Sometimes the QA urls can behave a bit strangely, so you could also QA against a live activity. Of course, you don't want it to be live to everyone, so that's why you apply the condition of "query string contains qa=true" to each of your audiences.So, for example, if Exp A currently has an audience ...

@Bazil_Wang - this support was added in at.js 2.7.0 so you need to be on that version or later

You should now have out of the box support, as long as you're using at.js 2.7.0 or later

That "View in Analytics" option doesn't work consistently in my experience. Do you have a screenshot of what you're seeing in the Target Reporting UI? i.e. the Activity-level numbers but not the Experience-level breakdown

One thing you might want to try is creating some QA audiences (e.g. query contains qa=true). Then you can apply those audiences to your activity/experiences, activate the activity and then validate whether you see the same issues. I've occasionally seen some odd behaviour with the QA links, so it wo...

Ok, so that means you're not qualifying for the activity, because you don't have the "options" array, which is what contains the activity/experience content (and also response tokens).For example, when I load a page and my activity content is returned in the response, I see this:

This should be possible without the SDK, as the SDKs are ultimately based on the Delivery API. This repo might be helpful, as it contains the Delivery APIs Open API spec & description

This should be relatively simple in a server-side implementation, the most simple option would be to create an activity that returns a JSON offer with something like....{currency: "£"}You would provide an mbox name as part of your server-side request to Target, and then your web application would pa...

I would suggest that you compare the Android implementation with the iOS implementation and see if there are any differences. It's difficult to troubleshoot without being able to look at all of the configuration.