Cookie Categorization Issue between Adobe & Onetrust

[Naveen_KumarPr1]

Hello Experts,

We recommended to client that "AMCV", "Demdex" & "EVEREST" should be categorized as "Analytics/Performance cookies". However client kept arguing with us, that Onetrust categorized the same cookies under "Advertising"/"Targeting cookies" 

We see that issue with behavior of cookies getting dropped when user blocks or unblocks consent for "Advertising" cookies

In Other words, we need to prove to client with a documentation from Adobe showing that we need categorize these 3 cookies as Performance cookies

*Note: We are using the Visitor ID opt-in service API 

Thanks in Advance. 

[bjoern__koth]

Hi @Naveen_KumarPr1 

TL;DR;
Maybe just open an Adobe support ticket to get their official recommendation / best practice.

The cookies surely have nothing to do with advertising, but however one could argue that targeting might sound plausible if you are using the cookie to play out personalized content on the website (e.g., throgh Adobe Target) and hence use this to reidentify the user.

To be honest, it is up to them to decide, so as long as the cookies that one tool is setting are in the same cookie consent category, that is just a different configuration.

Nevertheless, this should not impact your implementation, since it is just a different configuration you are applying to your Visitor service that handles which tools are allowed to fired based on the different consents you have configured.

https://experienceleague.adobe.com/en/docs/id-service/using/implementation/opt-in-service/optin-over... 

[Jennifer_Dungan]

These cookie ("AMCV", "Demdex" & "EVEREST") might be flagged since I believe they are shared across the Adobe tools, including Adobe Advertise... however, since AMCV and Demdex should be configured based on your own organization, and not shared to other orgs, unless you are using Adobe Advertising in your tech stack, this shouldn't be doing any sort of "advertising" actions...

I believe the Everest cookie is also tied to Adobe Advertising... I don't see that cookie being set in my own implementation.. so maybe you do have Adobe Advertising which is potentially "muddying the waters".... 

I agree with @bjoern__koth about contacting Adobe for their official stance on this...

Good Luck.