Hi Karan,Yes, in dev tools, the Network tab in particular, I can see a reference to the my test/experience in the Response Body. However, I'm also getting "ttMETA object does not exist" in console.The errors I'm seeing are related to:SEC7120: Origin now found in Access-Control-Allow-Origin header.SC...

@Mihnea - Thank you for the in depth explanation!!  I haven't needed to combine audiences in a while and actually forgot that you can do this.Works like a charm!!!- Brion

Hello Forum,Does anyone know if there is a way to exclude OSs from test entry? The following shows how to include: https://marketing.adobe.com/resources/help/en_US/target/target/c_operating_system.html.If not this way, wondering if it's possible to do it via Profile Script?Thanks in advance!- Brion

Hi all,I've got an A/B test activity in which I'm targeting Chrome, FF, Safari, Edge, and IE11. All browsers work with the exception of IE11.I can't determine what is wrong with my audience configuration. See attached.I've included an additional OR to include Browser Type equals IE and Browser Versi...

Awesome! Thanks, @russpainter!!

Hello Forum!I'm wondering if there is a way to automate the creation of test activities?Our team is trying to simplify our process, and this is one of the things I've been asked to investigate.Any help guidance is appreciated!- Brion

Happy to hear those of us experiencing this issue were able to quickly resolve it!surbgupt​ - thank you again for the suggestion! Our team will be making this a part of our process, particularly if/when a release appears to affect Target UI usability.

Good morning/afternoon,Is anyone having issues with Target Standard/Premium, where upon saving a change, an error message is shown stating: ERROR Referring to invalid nodes?After opening an activity to make a change to, I was greeted with this error message. Initially I thought it was the custom cod...

Thanks again RamH!I believe our flicker is a result of using a custom global mbox. We prevent flicker by setting the targeted content to '0' opacity, then change the opacity to '1' once Target fires--similar to what the Auto Created Global Mbox does, just not on the body.So, a few final questions:Do...

Thank you, Ram!We are currently using at.js, but still experience some flicker in tests.Considering the VEC and auto creating Global Mboxes, does the same apply with regard to the Form-based Composer? We use both VEC and FBC.It sounds like the best (only) way to avoid flicker is to use Auto Create?