How to set Target cookie with SECURE flag

[Khushboo_Kalia]

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!

[shelly-goel · Accepted solution]

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

[Khushboo_Kalia]

@shelly-goel Yes, I am trying on https pages.

[shelly-goel]

@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.

[Khushboo_Kalia]

@shelly-goel, thanks for getting back on this. Target implementation is done through Launch and I have tried setting other things through targetGlobalSettings within Launch rule which gives me expected results. On this particular issue, I have received the confirmation that setting the secure flag is not available in Target at present and will be considered as an enhancement to the tool.

[ryanr7]

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...