How to enable Adobe Target content delivery? | Community
Skip to main content
peter-g
peter-g
Level 2
April 20, 2021
Solved

How to enable Adobe Target content delivery?

  • April 20, 2021
  • 1 reply
  • 1037 views

I'm dealing with a console warning in Chrome which says:

VM582:1 AT: 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.

 I'm following the steps from the Adobe Target - Launch implementation guide here.

 

But I cannot validate the page load request - I never see a delivery request appear in my debugger despite following the guide. I do see that Adobe Target is present in my extensions and also that its using at.js 2.4.1 but for some reason the request never appears on refresh.

 

Is there some other pre-requisite steps I am missing which might cause this error? Does anything need to be configured in the Adobe Target UI or should it work with just the Launch steps from the guide?

 

Any help is greatly appreciated.

Thank you

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by ambikaTewari_ATCI

    Hi @peter-g this error usually comes when web url domain is not detected by cookieDomain . You need to manually set the domain name through window.targetGlobalSettings in cookieDomain like this :

     

    window.targetGlobalSettings =
    {

    var hostname=window.location.hostname;
    cookieDomain:hostname;
    }

    1 reply

    ambikaTewari_ATCI
    Community Advisor
    ambikaTewari_ATCICommunity AdvisorAccepted solution
    Community Advisor
    April 26, 2021

    Hi @peter-g this error usually comes when web url domain is not detected by cookieDomain . You need to manually set the domain name through window.targetGlobalSettings in cookieDomain like this :

     

    window.targetGlobalSettings =
    {

    var hostname=window.location.hostname;
    cookieDomain:hostname;
    }

      Terms & ConditionsAccessibility statement

      Loading footer...