When creating an audience to target experiences based on an mbox parameter value, there is very limited functionality for how the mbox parameter can be evaluated.It is only possible to directly compare an mbox parameter with a static value, which limits the ability to easily do personalisation on a segment-of-one basis. Meanwhile, it is possible to compare profile scripts and other attributes directly to attributes. See the below screenshot as an illustration of the two differences.Our need is t...

Our Launch Properties are used across multiple domains. In the AAM UUID Cookie configuration in the AA extension we need to be able to set the UUID Cookie Domain to be variable depending on the hostname of the page which is being viewed. Unlike most configuration values in the extension, this one does not allow the use of a Data Element and so we're not able to achieve this.

The archives created for manual deployments contain redundant folders (redundant in a self-hosting environment where you already know where you want to host the file and usually have a specific folder for it), and creates chaos for people using deployment tools or a CMS for publishing (regardless of which CMS it is). Our ops team are going to very quickly hate me because of the large amount of work this is creating for them every time we do a release.We need the ability to set an option so that ...

We're able to access certain event properties via the data element macro - such as the %event.detail.[abc]% object - but we can't seem to use this same approach for other components of the event object - such as event.target and event.elementIs there a particular reason for this, and is there anything which shows exactly what is and isn't available through the data element macro?

It's impossible for us to keep on top of CMS changes, and when using the VEC this can have wildly unexpected results when a change occurs to the page and the content authors can't test the page against all experiences being applied to the page.In the activity list/browser, we should have an easy way of identifying all active activities where the VEC is in use and there has been a change to the page/selectors and re-validation or adjustment is required. Alerts would also be highly useful.