GTM Community Template¶

The Waulter Community Template wraps the SDK in a point-and-click interface — no Custom HTML code required.

Installation¶

Step 1 — Add the template¶

From the Community Template Gallery (when available):

1. In your GTM container, go to Templates > Search Gallery.
2. Search for "Waulter consent management (cookie and other consents management)".
3. Click Add to workspace and confirm.

Manual import (recommended while Gallery approval is pending):

1. Download template.tpl from the Waulter GTM GitHub repository.
2. In GTM, go to Templates > Tag Templates > New.
3. Click the three-dot menu (top right) > Import.
4. Select the downloaded template.tpl file.
5. Click Save.

Step 2 — Create a tag¶

1. Go to Tags > New.
2. Click Tag Configuration and select Waulter consent management (cookie and other consents management) from the Custom section.
3. Fill in the required fields (see Field Reference below).

Step 3 — Set the trigger¶

Select Consent Initialization - All Pages as the trigger.

Step 4 — Preview and test¶

1. Click Preview in GTM.
2. Enter your site URL and open the preview.
3. Verify that:
   • The consent banner appears for new visitors
   • The gtm.init_consent event fires first
   • Default consent signals are all denied
   • After clicking "Accept All", Waulter:Decision fires with decision: "allow"
   • Consent-dependent tags fire only after consent is granted

Step 5 — Publish¶

Once verified, click Submit to publish your container.

Field Reference¶

Setting custom fields¶

Custom fields in the template accept any text value. You can use GTM variables to make them dynamic:

Auto-lookup with the scaffold¶

When the companion scaffold is imported, custom fields work automatically without additional GTM configuration. Each template field defaults to a scaffold Data Layer Variable ({{Waulter - Custom Field 1}} through {{Waulter - Custom Field 10}}).

Your website sets a value in localStorage or a cookie using the naming convention waulter_cf1 through waulter_cf10. The scaffold's Custom Fields Loader tag reads the value, pushes it to the data layer, the DLV picks it up, and the template passes it to WaulterConfig — all automatically.

// On your website — set a custom field value
localStorage.setItem('waulter_cf1', 'premium');
// That's it — the value flows automatically to scenario rules

Priority: If you replace a field's default DLV reference with a static value or different GTM variable, that override takes highest priority. Otherwise: localStorage > cookie.

Custom fields are used for scenario targeting and appear in all data layer events.

Google Consent Mode v2 mapping¶

The template maps Waulter consent decisions to Google consent signals automatically:

Permissions declared by the template¶

The template declares the following permissions in its manifest. GTM shows these during installation:

Updating the template¶

Gallery updates: When a new version is published to the GTM Community Template Gallery, GTM will show an Update available notification. Review the changes and click Update, then test in Preview mode before publishing.

Manual updates: Download the latest template.tpl from the GitHub repository and re-import via Templates > select the template > three-dot menu > Import.

Companion scaffold¶

The template works best with the Waulter GTM Scaffold — a pre-built container export with 79 variables, 17 triggers, and 2 tags covering all Waulter purposes and categories.

GTM Scaffold Guide

When to use Custom HTML instead¶

Use the Custom HTML approach if you need:

• Full control over which tags fire for which specific purposes (beyond GCM signal aggregation)
• Custom loading logic or timing
• Dynamic configuration from server-side rendering
• The appendDocument polling pattern for embedding legal documents
• Integration with an existing consent orchestration layer
• Strict regulatory compliance that requires purpose-level (not signal-level) tag control