How to control the firing of AAM in launch | Community
Skip to main content
P
pallavig
July 18, 2022
Solved

How to control the firing of AAM in launch

  • July 18, 2022
  • 1 reply
  • 2869 views

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! 

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 VaniBhemarasetty

@pallavig 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-cookies.html?lang=en

 

1 reply

yuhuisg
Community Advisor
yuhuisgCommunity Advisor
Community Advisor
July 19, 2022

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

    P
    pallavigAuthor
    July 20, 2022

    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! 

    VaniBhemarasetty
    Adobe Employee
    VaniBhemarasettyAdobe EmployeeAccepted solution
    Adobe Employee
    July 27, 2022

    @pallavig 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-cookies.html?lang=en

     

      Terms & ConditionsAccessibility statement

      Loading footer...