Yes, correct you should see a second call, could you share the code that you're using?The mbox doesn't have to be called "conversionTest", you can name it anything; you can just type it into the field even if it doesn't already exist, so I can add a new mbox called newMboxName and it's not a problem...

Probably a couple of different ways of doing this:i) Pass the HTML Language value as an mbox parameter and then you could create 3 separate XT experiences, with an audience based on that valueii) Create the activity with a single experience but use custom code, with some conditional logic based on t...

I'm guessing you've seen this example already? A more simplified version of that example, if my event tracking mbox is called "conversionTest", could look something like this:  alloy("sendEvent", { xdm: {}, decisionScopes: ['conversionTest'] }).then(function(result) { var propositions = result...

Yes, Bulk API would make a lot of sense in this scenario. Two things to keep in mind:i) Make sure to include productPurchaseId with the list of productsii) You can reduce the number of requests by ignoring orders with only one product, as they of course don't add any value to that particular algorit...

It's not supported in the same way in Web SDK (see here), so it would be something where you would need to control the sequencing of the requests i.e., first make a request to the API of whichever data provider you need and then include that data in either the XDM or Data object that you pass in you...

How are you creating your Target activity? If you're creating it via the Visual Editor then you would only see HTML Experience Fragments when using that "Replace Content > Experience Fragment" option

Lift is also referred to as Minimum Detectable Effect (MDE); there are a lot of good articles that talk about this in detail but effectively it reflects the change in conversion rate you expect from your variant; the required sample size becomes smaller as the MDE becomes bigger.As part of the calcu...

The main focus should be on the individual experience-level calculations vs the Control

As a general rule of thumb it's profile data & Recommendations data that would be sent via the data object; however, this page gives a good overview of in which scenarios you should use XDM & in which scenarios you should use the data object.

The Baseline Conversion Rate will be the current conversion rate (Metric/Visitors) for the Metric that you're optimising against. So if your test hypothesis is focused around increasing Form Starts, then you would take Form Starts/Visitors to find your baseline conversion rate. As you mention, you s...