This extension is only compatible with App Connect 1. I don’t have a timeline to make it compatible with App Connect 2.
Before using this extension make sure you have gone through the library’s documentation so you understand what’s and what’s not possible and how to achieve your objective.
This Wappler component wraps the library for compatibility with App Connect while providing a UI to interact with it from the Studio app.
Once the user accepts the analytics category in the consent modal it will load the script. If the user doesn’t accept the analytics category the script will never run so the analytics cookies won’t be placed in the user’s browser.
For weeks now I’ve been getting a Google reminder that our existing cookie/tracking GDPR response needs updating. I’ve never been happy with it but have been reluctant to start researching what else was available out there - then this drops into my lap!!
I’ve just (easily) installed the extension and its working as an absolute dream - there are so many options in there - it’s great. Thanks for taking the time to create this extension, I’m sure it’ll be really popular.
I’m really happy you are finding it useful and easy to use. I poured a lot of time in adding extra information to the UI and adding the myriad of options.
There are a few advanced options that I haven’t been able to figure out how to implement in a user friendly way due to the limitation of some UI controls that Wappler provides. So I need to give it further thought or maybe push for some additional UI controls from Wappler.
Had I built this to suit only my needs the UI configuration file would have been like 5 times smaller and the overall logic less extensive and polished. But to make it useful for the community the work involved starts growing very fast.
The only addition I could see that would be useful would be a modal editor to allow editing of the wording on the modal itself (Header, Description, Footer), maybe include it in the ‘UI Customization’ section…? I cant see right now where that’s done,
It’s up to you. Both options are possible.
I would advise you to go through the library official documentation on how to accomplish each one of them.
This extension just wraps the library so it’s compatible with App Connect and provides a UI so it’s usable from Wappler.
I just looked into this a bit more and wanted to confirm I have it right. I followed
So I add
<!-- Global site tag (gtag.js) - Google Analytics -->
<script type="text/plain" data-cookiecategory="analytics" async src="https://www.googletagmanager.com/gtag/js?id=GA_MEASUREMENT_ID"></script>
<script type="text/plain" data-cookiecategory="analytics">
window.dataLayer = window.dataLayer || [];
function gtag(){window.dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'GA_MEASUREMENT_ID');
</script>
to the head of my layout page and then add a new category to match the data-cookiecategory like
Just a quick update, I received an email from Google today regarding compliance. They are soon to be implementing a management policy that will only allow consent management from a verified platform - read more here: https://support.google.com/adsense/answer/13554116
That’s correct but anyone who builds one will have to have it Google certified before deploying it if they use any Google services (AdSense in our case).
Yep. What I’m trying to say is that this library(Orestbida) is not a CMP and probably will never be one. And if the author decides to build a CMP based on his library it would be another product.
In other words, I’m afraid to say that this library and the extension won’t help you with your google ads problems unless the author decides to build a CMP based on the library and he gets certified.