For technical teams

A CMP built for data and dev teams

Most CMPs are built for marketing teams clicking through a dashboard. Waulter is different — consent as first-class data in your pipeline, configuration with DEV and PROD environments, automation via API and an MCP server.

Data Track — consent state in your pipeline

Rich event system

The Waulter SDK fires detailed consent events at every step of the consent lifecycle. No black boxes:

Event	When it fires	Key data
gtm.init_consent	SDK starts	Default consent state
Waulter:Loaded	Config received	Custom fields, CCID
Waulter:Open	Banner shown	Custom fields
Waulter:Decision	User decided	decision, purposes[]
Waulter:Closed	Banner closed	Custom fields

Every event is available in two formats: dataLayer.push() for GTM and DOM CustomEvent for direct JS listening.

Consent as first-class data

Purpose codes — every consent broken down into specific purpose codes, not just "accepted/rejected"
Google Consent Mode mapping — purpose codes automatically map to analytics_storage, ad_storage, etc.
10 custom fields — pass context from your site into the SDK: user type, pricing tier, page category
Backend events — server-side analytics independent of the client

Audit-ready logs

Consent event — decision, accepted purpose codes, page URL, timestamp
Document versions — cookie policy version in effect at the time of consent
Identification — encrypted consentizerId (ASP.NET Data Protection)
Expiration — automatic consent validity monitoring (default 90 days, maximum 12 months)

Dev Track — consent config in your workflow

Templates and DEV/PROD workflow

Custom templates — create a banner template once, apply to any number of domains
Versioning — every configuration change is versioned, rollback is a single operation
DEV and PROD configurations — test on a staging configuration, then switch the scenario to production.

Batch operations and domain management

Configuration templates — create once, apply via API to any number of domains
Bulk updates — change settings across 50 domains with a single API call
Access delegation — share configurations with colleagues, agencies, legal teams

Legal docs as code

Edit documents in the B2B zone; new versions via API on request for Enterprise
Roll back to a previous version
Distribution via SDK — the banner links to the current version automatically
Full version history with timestamps

Custom Templating

Templates are the foundation of scaling. Create a banner template, processing purpose configuration, or legal document set once — and apply it to any number of domains.

Banner templates — design, copy, behavior, and scenarios in a single template. Changes propagate to all connected domains.
Purpose templates — predefined sets of processing purposes for different site types (e-commerce, blog, SaaS).
Document templates — cookie policies and privacy notices tailored to your industry.
Bulk application — apply a template to 50 domains with a single API call. See batch operations.

MCP server is live

Both tracks meet in MCP — automation for data and dev workflows via a standardized protocol used by Claude Code, Codex and other tools.

More about the MCP server

Who Waulter is built for

CTO / Tech Lead

API-first, versioned documents, DEV and PROD configurations, infrastructure-as-code approach to consent management. API documentation available on request for Enterprise.

Data Engineer

Structured events in the datalayer, purpose codes mapped to Google Consent Mode signals, backend analytics events.

DevOps

Batch operations, templates, API access, MCP automation. Manage 50 domains without clicking through a UI.

DPO / Compliance

Full traceability — who consented, when, to what, and under which document version.