Getting warning for Adobe Target content delivery is disabled. Ensure that you can save cookies to your current domain, there is no "mboxDisable" cookie and there is no "mboxDisable" parameter in query string.

[SandeepSi]

Getting below warning for Adobe Target :

AT: [page-init] Adobe Target content delivery is disabled. Ensure that you can save cookies to your current domain, there is no "mboxDisable" cookie and there is no "mboxDisable" parameter in query string.

- We implemented Adobe Target (V2) integration using Data collection tags . During initial set up also we were getting same error . Then through community forums got resolution that we need to set cookie domain and made below changes . Post this target calls were getting fired (were able to see the calls in experience cloud debugger) and created activities in Target were working.

window.targetGlobalSettings =

{

cookieDomain:window.location.hostname

}

Then after one month (we didnt make any change) we started session error for  "sessionId query parameter is ". As session ID we are not managing so not sure how to resolve this issue. We updated the extensions also but it didnt work. 

Now we have reimplemented the Target set up (using data collection by creating new property , adding extensions , datat elements and rules). Now not getting Target page load call in exp cloud debugger.In Consloe seeing the warning for 

AT: [page-init] Adobe Target content delivery is disabled. Ensure that you can save cookies to your current domain, there is no "mboxDisable" cookie and there is no "mboxDisable" parameter in query string.

Any suggestion would be helpful.

Thanks & Regards 

[alexbishop]

It sounds like you might have 2 mbox cookies, there are two common causes for this.

One cause is that there is a cookie from the old library and one from the new library; the format of the cookie from each library is slightly different, which causes this error. However, the same error can also be caused by the Chrome Visual Editor extension.

So the first step would be to check if you're seeing 2 mbox cookies; if you see 2 mbox cookies and you are also using the Chrome Visual Editor extension, try loading the same page in an incognito window where the extension isn't active and see if 2 cookies are still set. If they aren't then the problem is likely just the Visual Editor extension, rather than something your visitors will experience. 

[rupaljain2408]

Hi Sandeep, 

Did you find solution to this problem?

I am also facing the same.

Best Regards,

Rupal