Adobe Target Community Q&A Coffee Break: On Wednesday, February 1 at 8am PT, Brent Kostak of the Adobe Target Product team will be joining us to answer your Target questions. To register and for more information, follow the link to the right.
My Page is loading with all 3 parameters mboxDisable=1, mboxEdit=1 but I can see Target is firing inside VEC composer "mboxDisable=1" parameter worked fine by itself, until paired with "mboxEdit=1"
Maybe you still have something from a QA link in the cookie. I would delete this if necessary or try it in the Incognito Window. Here is also a post on how you can have mboxes disabled via session cookie. However, this generally only works with the at.js. When using the Mobile SDK, the mboxDisable option does not exist.
