GTM Consent Initialization Trigger Explained

Consent Initialization is the early GTM moment reserved for consent setup. If your CMP or consent defaults run too late, normal tags may start before they know the visitor's consent state.

What the trigger is for

The Consent Initialization trigger is designed for tags that establish consent state. It should run before normal page view, analytics, advertising, and conversion tags.

What should fire there

Your CMP tag or consent setup tag should run there if you use GTM for Consent Mode. The goal is to set defaults early and make previous stored choices available before other tags evaluate consent.

What should not fire there

Consent Initialization should not become a place for ordinary analytics or marketing tags. If everything fires there, you lose the timing advantage and make debugging harder.

How to test it

Open GTM Preview and inspect the first events. Your consent setup should appear before normal tags. Then test reject, accept, reload, and a stored consent state.

How CleanCMP fits

CleanCMP's GTM install path is designed around early consent setup. You use the CleanCMP template, add the site-specific install URL, and fire the tag on Consent Initialization - All Pages.

FAQs

Do I need Consent Initialization if I hardcode CleanCMP?

If CleanCMP is loaded directly before GTM, your setup may not need the CMP tag itself inside GTM. The timing still matters.

Can GA4 fire on Consent Initialization?

Ordinary analytics tags should not be placed there just to make them early. Use it for consent setup.

What is the common mistake?

Running the CMP after normal page view tags, then wondering why cookies or requests appear before the banner choice.

Set it up in CleanCMP

CleanCMP gives you the banner builder, cookie scanner, GTM install path, Consent Mode v2 signal mapping, proof records, and reporting in one focused workspace.

Create account