We use OneTrust and the script is within the theme itself. It should not be setup via GTM or a pixel as you need to make sure whatever platform you use always triggers before other scripts, so in the theme itself.

Hi @Dabrowka ,I did a custom solution with our developer and it works now with Custom Pixel. Here are steps: 1. Default command is triggered within the Custom Pixel and always set to "denied".2. I use Simo Ahava's consent update command within GTM an...

Unfortunately not. I've tried many stuff but couldn't get the engagement time going. One other thing I'll try which is a long shot is that we have duplicate dataLayer, meaning one is still on top where the Consent Management Platform creating and one...

Have the same issue where engagement time doesn't appear and shows as 0. Made some changes and sending send_page_view false in Config tag and sending separate page view tag, which helped us see the user_engagement events finally, however it still sho...

We made the decision to not go with that initially before we were switching to Checkout Extensibility. Now I regret not moving with that option, would make our lives way easier for sure. If nothing works, most likely will switch to Elevar as well.

We have the same problem, we used to set default and update commands trough Simo Ahava's consent mode v2 tag in GTM. The tag is not working correctly anymore, which requires a page load for it to send the update commands correctly, even if the cookie...