A: Thanks for the follow-up. I now see that both the GTM source detection issue and your earlier question about overriding the default consent state are related. That context helps a lot.

As mentioned before, CookiePal is built to follow GDPR standards, which is why we do not allow forcing a “granted” default without user interaction. That said, there is a custom script option that allows more control for advanced setups, and we are happy to help you implement it if needed.

Regarding the GTM detection issue you reported on August 20, this is now confirmed as a technical bug affecting some setups. It is not specific to your account, and we are working on a fix. A new tool is being integrated to improve both GCM verification and cookie scanning, which will resolve this more reliably going forward.

I fully agree that our lack of follow-up was not acceptable. I will make sure you get the proper support moving forward. If you would like, I am happy to personally walk you through the workaround using the custom script or assist with verifying your GTM setup manually.