Cookie banner & accessibility via Tag Manager
It works, with a catch: Tag Manager starts first, so tags that fire before the widget aren’t held. If you can edit your site’s <head>, put the snippet there instead (Custom code guide).
Installation steps
Add a Custom HTML tag
In Tag Manager add a new tag: Tag type Custom HTML, and paste the snippet.
Fire it on Consent Initialization
Trigger: Consent Initialization - All Pages. Save, then Submit to publish the container.
Make your other tags wait for consent
In Tag Manager, give each analytics and marketing tag a consent requirement (Advanced settings › Consent settings), so it fires only once that consent is granted. With Google Consent Mode v2 on in your ComplyMo cookie settings (it is by default), the widget passes the visitor’s choice to Tag Manager.
Better: paste it first in <head>
If you can edit your site’s code, put the snippet first in <head>, above Tag Manager, as in the Custom code guide. Then auto-block holds supported trackers too.
Copy your snippet from Install in your dashboard (Home, or a site's Widget tab) and put it first in the <head>, before any analytics tag.
Why <head> is safer
Loaded through Tag Manager, the widget starts after Tag Manager itself, so auto-block can’t stop tags that fire first. Set your analytics and marketing tags to wait for consent in Tag Manager, or paste the snippet straight into <head> instead.
Loaded first in <head> (Custom code guide), the widget runs before Tag Manager and auto-block holds known trackers by itself.

