WebmasterID Docs

WebmasterID Privacy & GDPR

WebmasterID is designed to be lightweight and privacy-conscious, but no analytics tool makes a site compliant on its own. This page explains how to integrate it the way helperg.com does: consent-gated under Google Consent Mode v2.

Google Consent Mode v2

helperg.com sets all consent signals to denied by default before any tag loads:

gtag('consent', 'default', {
  'ad_storage':         'denied',
  'analytics_storage':  'denied',
  'ad_user_data':       'denied',
  'ad_personalization': 'denied',
  'wait_for_update':    500
});

When the visitor accepts the Analytics category, the consent manager updates analytics_storage to granted. Until then, analytics stays denied.

Consent-gated loading

WebmasterID is not placed statically in every page. It is injected once by the cookie consent manager, and only when Analytics consent is granted:

// inside the consent manager, after analytics consent is granted
if (consent.analytics) { loadWebmasterID(); }

function loadWebmasterID() {
  if (document.getElementById('webmasterid-tracker')) return;
  var s = document.createElement('script');
  s.id = 'webmasterid-tracker';
  s.defer = true;
  s.src = 'https://webmasterid.com/tracker.iife.min.js';
  s.setAttribute('data-wmid', 'wm_xxxxxxxxxxxxxxxx');
  s.setAttribute('data-endpoint', 'https://webmasterid-ingest-api.vercel.app/api/events');
  (document.head || document.documentElement).appendChild(s);
}

Consequences of this design:

  • No analytics request is made before consent.
  • The tracker loads once per page (guarded by the element id), with defer so it never blocks rendering.
  • Visitors who decline or ignore the banner are never tracked by WebmasterID.

Lightweight analytics positioning

WebmasterID intentionally collects a minimal set of website events and sends them to an endpoint the site owner controls, rather than distributing data across many third parties. Owned, minimal analytics is easier to reason about for both visitors and operators — but it complements, and does not replace, your legal consent and privacy disclosures.

Troubleshooting

  • Tracker never loads: confirm the Analytics category is actually being granted and that the consent manager calls the loader on grant and on consent restore for returning visitors.
  • Loads before consent: remove any static script tag; the only injection path should be the consent-gated loader.
  • Request blocked: allow the ingest endpoint in your CSP connect-src.

FAQ

Is WebmasterID GDPR compliant by itself?

No analytics tool makes a site automatically compliant. It is designed to be privacy-conscious, but you are responsible for consent and disclosures. Load it only after analytics consent.

Does WebmasterID replace my cookie banner?

No. It is analytics, not consent tooling. Run it alongside your consent banner, not instead of it.

How does helperg.com gate the tracker?

The tracker is injected once by the cookie consent manager only after the visitor accepts the Analytics category, consistent with Consent Mode v2 defaults of denied.

Related

Installation overview · HTML installation · Next.js installation · What is WebmasterID?