Typically this would be caused by one of two problems:i) You're not qualifying for the activityii) You're qualifying for the activity but the modifications aren't being applied (i.e., selectors aren't valid)So it would help to narrow things down by working out which one of those two it is. Can you c...

This document should give you a good overview of how they compare 

The short answer is no - the problem is that AMP pages are cached and server from Google's edge network, which means that no call is made to Target

Typically you would just optimize against a single metric (i.e., Form Completions) and then look at other supporting metrics/segments/dimensions to get both a broader, but also more detailed, understanding of test performance. So you would ideally use that Primary KPI of Form Completions in the init...

Great that it works now - there isn't any existing configuration for storing the profile.tntId value, so you would just need to write your own JS to do that

It most likely means the Response Token for profile.tntId isn't active then; if you go to Administration > Response Tokens you can check the status, and if it shows Deactivated then click the toggle button to activate it:

You'll only see data relevant to Target in the response if it's a page that qualifies for a Target activity and therefore the response contains activity information. In your screenshot the payload is empty for that "personalization:decisions" event type, which suggests you're not qualifying for any ...

You would read the individual experience level confidence % and then compare that against the confidence level that is set. By default this is 95% but you do have the option to export results data and adjust this (as mentioned here). It's also important to calculate the required sample size before s...

Sounds a little odd as I'd expect there to be just one value everywhere in Analysis Workspace. Those "friendly name" values are being set by the TnT classification file, so an admin user can go to Admin > Classification Importer, export the TnT classification file and check what values there are in ...

You can access it via the Response from the Web SDK request (see example here). Part of that response contains a meta object, which includes profile.tntId (and other response tokens that are enabled):