Expand my Community achievements bar.

Join us for the Adobe Journey Optimizer Community Q&A Coffee Break on 28th February at 8 am PT with Ariel Sultan, Daniel Wright, Josee Haeley and Rohit Basuri.
SOLVED

How to control the firing of AAM in launch

Avatar

Level 1

What is the best way to control the firing of AAM in adobe launch? Cookies like demdex and Everest are dropped by Adobe audience manager which we want to make sure are only dropped when the user has only consented for advertising cookies. We are individually approving all the extensions in the Opt in services code. However, AAM is firing even when it is not approved, inconsistently seen to fire alone by ECID approval, unless the disabled parameters are set in the ECID extension (Screenshot attached). We don't want to use the patch work of adding disabled variables as it has a trade off in other area. Any thoughts/ideas would be highly appreciated. Thank you! 

Screenshot 2022-07-18 at 15.35.22.png

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

@Pallavi_1 You can use disableThirdPartyCookies functions to not set demdex cookie on your browser by ECID service, in a you are hiding the demdex call, which is used to create the MID 

https://experienceleague.adobe.com/docs/id-service/using/id-service-api/configurations/disable-cooki...

 

View solution in original post

5 Replies

Avatar

Community Advisor

I think what you're seeing -- cookies being set -- is not because of AAM, but ECID. See https://experienceleague.adobe.com/docs/id-service/using/intro/cookies.html?lang=en and https://experienceleague.adobe.com/docs/id-service/using/intro/id-request.html?lang=en. These detail how cookies are set/used by ECID, in particular, to identify visitors consistently when used across domains.

To check if ECID is really the culprit, try unselecting its Pre Opt in approval as well.

FYI Jan Exner has great articles on ECID's opt-in workflow. You probably already know these details, but they're still great references to bookmark. https://webanalyticsfordevelopers.com/2021/02/16/consent-and-launch/ and https://webanalyticsfordevelopers.com/2021/06/01/consent-and-launch-part-ii-opt-in/.

Avatar

Level 1

Thank you! That was helpful. I see demdex cookie is unrelated to AAM. Although, I couldn't read a lot about the disable variables within ECID extension, why and when to use them and trade-offs.

It was our intention to stop using them and we are only using it to prevent AAMs from firing in functional consent. What other options are there to stop AAM from firing? I have used Optin service and denied AAM specifically in the respective rule but that did not help as ECID alone is able to fire AAM. Looking forward to hearing your thoughts. Thanks! 

Avatar

Community Advisor

You're assuming that the demdex and everesttech cookies are set by AAM only. As I've mentioned above and also as mentioned in my linked articles, these cookies can be set by ECID too.

So if you don't want to see these cookies until consent has been given, then you need to disable ECID too, using the Pre Opt In checkboxes in the extension configuration. Read Jan Exner's articles too for a refresher on how to use these with consent.

Avatar

Correct answer by
Employee Advisor

@Pallavi_1 You can use disableThirdPartyCookies functions to not set demdex cookie on your browser by ECID service, in a you are hiding the demdex call, which is used to create the MID 

https://experienceleague.adobe.com/docs/id-service/using/id-service-api/configurations/disable-cooki...

 

Avatar

Level 6

@Pallavi_1  - disableThirdPartyCookies functions to not set demdex cookie affect existing Adobe analytics server call? or will it have any other impact in metrics capture?

Thanks in Advance .