Glad that you found the root cause - it makes sense that a CNAME implementation wouldn't work on localhost without SSL

Are you still seeing this issue? If so, can you provide some more details on your implementation? If you haven't already, I'd recommend using Assurance to validate whether or not the stitching is happening at the Edge, as that will help to narrow down the root cause. Whilst the documentation largely...

If the tntId isn't persisting then it's certainly a broader implementation issue, not an issue with profile scripts per se. I can also see that the marketingCloudVisitorId is different in the screenshot. Is the checkout page on a different sub-domain/domain vs the other pages?

It isn't possible to set up a multi-variate test using the form composer. Having said that, you can continue to use HTML offers as part of the VEC-based MVT workflow. So how feasible that approach is depends on how much of a blocker having no JSON offers is, as well as how exactly you're leveraging ...

Do you want to measure this through Adobe Target reporting or with Adobe Analytics?

I understand the confusion, given the name of the extension, but the way to implement Target in Mobile App via Edge is by using the Decisioning Extension - see full details here 

Ah ok so it's a CDP audience being shared to the Target destination. In that case I'm wondering how you have implemented Target in the Mobile App. You'd need to use the Platform Edge and Journey Decisioning extensions in order to utilise that CDP audience; I'm wondering if you've implemented the Tar...

Could you give a bit more information on why you can't use the Visual Editor? What type of modifications are you making in the AB test?

This isn't expected behaviour; I've also tried to replicate this on a demo page with Target but I can't. The first sendEvent that happens on my page contains the "__view__" global mbox decisionScope, then I run your example code in the console but I only see "hero-banner" in my decisionScopes array,...

When you say "experience fire twice", do you mean that you see 2 requests to Target, and therefore the content returned from Target is rendered twice? Or a single network request to Target but still the content rendered twice? And do you see the issue if you don't use the QA link? e.g. if you apply ...