Expand my Community achievements bar.

Disabling first *and* third party cookies set by at.js

Avatar

Level 1

Hello,

 

We would like to disable both first and third party cookies set by Target, that is no cookies at all set by Target, for some of our site visitors.  Is there a way to set something in TargetGlobalSettings to stop all first and third party cookies being set? I know there is a setting for third party cookies, "cookieDomain", but our requirement is different.

 

We would like to run the at.js script directly in our index.js, not in GTM, our tag manager.

 

Thanks in advance

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

6 Replies

Avatar

Level 7

@AdamBa17 Adobe Target’s at.js might allow you to disable third-party cookies through a configuration option. Please check Adobe documentation for more details 

Avatar

Level 1

Thanks. To clarify I would like to disable first party cookie persistence in at.js.  How to do this?

Avatar

Administrator

Thank you for posting your question here AdamBa17And thank you Rite18 for weighing in! AdamBa17 were you able to resolve the issue? If so, please feel free to share any updates or follow up Qs here by Replying to the thread so that others with similar issues can refer to your approach!

 

Otherwise Rite18 do you have any other suggestions here? Thanks!

Avatar

Level 1

HI @Amelia_Waliany , thank you for following up. I was not able to resolve the issue through here or Adobe support.  There appears to be no way to stop Adobe Target setting the mbox cookie as the script loads.

Avatar

Level 7

@AdamBa17  would like to know the use case why you want to disable 1st party cookie ? How you are planning to use target then if cookies are disabled.

you can think of custom solution to delete cookie using Java script if not able to disable thorough at.js - , cookies stored to companydomain are 1st party and you can target to delete them

Avatar

Level 1

Thank you for your reply.

 

It's for regulatory reasons in the EU region. You can read more about it by searching up GDPR.

 

This idea of deleting the cookie occurred to us previously, but after full consideration it is not robust enough to be a desirable enterprise solution for us.