Concerns Implementing Google Consent Mode v2 With OneTrust in Adobe Launch Hi Data Collection community! I'm trying to implement Google Consent Mode v2 with OneTrust as my consent management platform and I am using Adobe Launch instead of GTM. Previously I was using the GTAG extension by Acronym, but this extension seems to inject GTAG scripts for Google accounts (Google Analytics, Google Ads, etc.) into the `<head>` of my web application in an order that does not abide with what OneTrust documentation states. I have even reached out to OneTrust support and they seem to agree that we are not able to use the GTAG extension for that reason (although they did not sound too confident in that confirmation). Due to that, I have been testing abandoning the GTAG extension and including most of what the extension was doing in the `<head>` of my web application. Now, Adobe Launch is only responsible for sending GTAG events using Custom Code actions. However, after testing this refactor, I am noticing that GTAG scripts are