Skip to content

Implementation

Waulter can be deployed in several ways. Choose the approach that fits your technical setup and team.

Comparison

Approach Best for Flexibility Code required?
GTM Community Template Most teams High (point-and-click) No
GTM Custom HTML Advanced GTM users Full Minimal
Direct script tag Headless CMS, SSR apps, custom stacks Full Yes
Platform-specific Webflow, WordPress Moderate Minimal

The fastest path — install the official Waulter template from the GTM Template Gallery. No code required.

GTM Community Template

GTM Custom HTML

Full control over SDK initialisation using a Custom HTML tag. Use this for advanced patterns like appendDocument, dynamic custom fields, or integration with existing consent logic.

GTM Custom HTML

Direct Script Tag

Add the SDK directly to your HTML. Works with any website — static HTML, server-rendered apps, headless CMS, or SPAs.

Direct Script Tag

Platform guides

Platform Guide
Webflow Webflow Integration
WordPress WordPress Integration

How the SDK initialises

Regardless of deployment method, the SDK follows the same initialisation flow:

flowchart LR
    A["SDK script loads"] --> B["Reads WaulterConfig"]
    B --> C["Fetches configuration from server"]
    C --> D["Sets GCM default: all denied"]
    D --> E{"Existing consent?"}
    E -->|Yes| F["Updates GCM signals from stored consent"]
    E -->|No| G["Shows consent banner"]
    G --> H["Visitor decides"]
    H --> I["Updates GCM signals"]
    F --> J["Page continues"]
    I --> J

Prerequisites

Before deploying, ensure you have:

  • [x] A Waulter account with access to the dashboard
  • [x] A Configuration ID (e.g. AG0000) or Scenario ID (e.g. SC00009)
  • [x] Your domain added to the Whitelisted Domains list in the dashboard
  • [x] Access to your website's code or tag manager

See Getting Started for a full orientation.