Implementing OneTrust with Web SDK We recently implemented Web SDK. We have Analytics, Target and AAM. We will be implementing RTCDP soon. We also recently got OneTrust. We did a OneTrust scan of our website and came up with a list of cookies. In OT, cookies are categorized as Essential, Functional, Targeting, etc. Visitor preferences for each category are stored in a data layer variable. Therefore, we can inspect the variable to see that was opted in and out for each visitor; e.g. Essential opted in, Functional opted in, Targeting opted out, etc. We can have a script that either allows cookies to be created or not based on the category preferences (opted in or out). In Launch, we have a Page View rule. Based on my research, Web SDK creates multiple cookies such as-kndctr_<ORG_ID>_identity - Functional cookiekndctr_<ORG_ID>_consent - Targeting cookiekndctr_<ORG_ID>_cluster - Functional cookiembox - Targeting cookiemboxEdgeCluster - Targeting cookieAMCV_###@AdobeOrg - Targeting cookie OT