I've seen customers typically go one of two ways in this scenario:i) Reload the whole page on-click of accept consent, which then will allow for the pre-hiding snippet & Target to run as per normal page load process; having said that, Target via GTM has its own challenges due to GTM being loaded asy...

Could you give an example of which parameters you're referring to? And also ideally a screenshot showing where in the request to Target the parameters are being passed?

A bit tricky to say but it's possible that the element is being hidden behind other elements when using the Move action - see here for a bit more info around Re-arrange vs Move

If you haven't seen it already, this document explains how to set up multi-page tests

It's a bit difficult to diagnose without seeing the activity setup & the implementation; however, two possible causes that I can think of: i) When you make the modification in the Visual Editor, change the selector so that it targets the element ID (rather than the selector that Target automatically...

You would need to make an additional request to Target, after the "hasactivehealthplan" value is available. The challenge with that will be, if you are displaying the experiment content on the same page after the response from Target then you will see some flicker and would need to handle that

Yes, you're correct that those purchase parameters are sufficient; in case you haven't already seen it, this document gives a good overview of how you should send those 3 values as part of the XDM object. There are certain Target parameters, particularly relating to Recommendations, that do need to ...

You could set this up in Target but it would need to be done through a Custom Code modification, as opposed to using the standard Visual Editor actions

I'd expect that everything will work from a technical point of view but the big problem, as you alluded to, is the delay that this will introduce and the impact of that against personalisation activities that change page content. GTM can only be loaded asynchronously, so even loading Target directly...

Typically I've seen customers coming up with a proxy for a bounce and sending an event with a named mbox to Target when that thing happens i.e., time spent on page or an interaction indicating engagement. You could then configure your goal as "Conversion -> Viewed an mbox -> <named-mbox>". By no mea...