How to set Target cookie with SECURE flag | Community
Skip to main content
Khushboo_Kalia
Adobe Employee
Khushboo_KaliaAdobe Employee
Adobe Employee
December 1, 2020
Solved

How to set Target cookie with SECURE flag

  • December 1, 2020
  • 2 replies
  • 3007 views

Hi,

I want to set a secure flag for my Target cookie and have tried the below method but it is not working. Could anybody share their thoughts on how to get it worked?

  • Added a custom code before 'Load Target' action is added in Launch rule.
  • Here is the script which is the part of above mentioned custom code -

window.targetGlobalSettings = {
secureOnly: true
}

The above mentioned method seems to be not working when I checked using chrome developer tools where I found empty value for the column SECURE.

We have also tried enabled:false to validate the above method which is working as expected as it is disabling the Target library.

Is there any other method to set this flag for Target? As for Adobe Analytics and ECID, this setting is present directly on editing the configurations for the respective extensions in Launch but for Target there is no direct way. 

Your timely help is well appreciated. 

Thanks in advance!

    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 shelly-goel

    @khushboo_kalia  Since secure flag can be set and available only on https pages, I hope you're trying on https pages?

    2 replies

    shelly-goel
    Adobe Employee
    shelly-goelAdobe EmployeeAccepted solution
    Adobe Employee
    December 8, 2020

    @khushboo_kalia  Since secure flag can be set and available only on https pages, I hope you're trying on https pages?

      shelly-goel
      Adobe Employee
      shelly-goelAdobe Employee
      Adobe Employee
      December 17, 2020

      @khushboo_kaliaYou can try (if not already) adding window.targetGlobalSettings logic in at.js header in Target itself i.e. under Administration > Implementation > Edit at.js Settings > Code Settings > Library Header. There's a possibility that the value is getting overridden.

      R
      Adobe Employee
      ryanr7Adobe Employee
      Adobe Employee
      January 5, 2021

      As a point of clarification, the targetGlobalSettings of secureOnly: true does not impact the Target set cookies (mbox, etc.) it forces all the requests made from at.js to always be over HTTPS (secure protocol). Noted here in help: https://experienceleague.adobe.com/docs/target/using/implement-target/client-side/functions-overview/targetgobalsettings.html?lang=en#section_9AD6FA3690364F7480C872CB55567FB0

        Terms & ConditionsAccessibility statement

        Loading footer...