Skip to main content
HELPERG
WebmasterID Docs

WebmasterID Installation Overview

WebmasterID is lightweight website analytics that records website events and sends them to an endpoint you control. Installation is one small script — no build step required. This page explains what to install and how to choose a method.

What you are installing

WebmasterID is a single deferred tracker script that posts events to a configured ingest endpoint. It does not pull in a heavy SDK and does not require a framework. You configure two values:

  • data-wmid — your WebmasterID site ID (looks like wm_xxxxxxxxxxxxxxxx)
  • data-endpoint — the ingest endpoint events are sent to

Choose your integration

  • HTML installation — the universal method. Works on any static site or framework, including this one.
  • Next.js installation — add it with next/script, plus an optional component form if the package is available.
  • Privacy & GDPR — consent-gating, Consent Mode v2, and lightweight positioning.

The tracker, in one tag

Every method ultimately loads the same tracker. The canonical, framework-agnostic form is:

<script
  id="webmasterid-tracker"
  defer
  src="https://webmasterid.com/tracker.iife.min.js"
  data-wmid="wm_xxxxxxxxxxxxxxxx"
  data-endpoint="https://webmasterid-ingest-api.vercel.app/api/events">
</script>

Replace data-wmid with your own site ID. The defer attribute keeps it off the critical rendering path.

Privacy-safe by default

WebmasterID is designed to be privacy-conscious, but you are still responsible for consent in your jurisdiction. The recommended pattern is to inject the tracker only after the visitor grants analytics consent. On helperg.com the tracker is added once globally by the consent manager and fires only after Analytics consent under Google Consent Mode v2. See Privacy & GDPR.

Troubleshooting basics

  • No events: confirm analytics consent was granted (if you consent-gate it) and that data-wmid / data-endpoint are set.
  • Duplicate events: ensure the script is added once globally — guard against injecting it on every component or every navigation.
  • Blocked request: check that the ingest endpoint is reachable and not blocked by a content blocker or CSP connect-src.

FAQ

Does WebmasterID require a build step?

No. The universal method is a single script tag, so it works on any static site or framework without a build step.

Should the tracker load before or after consent?

For privacy-safe setups, load it only after the visitor grants analytics consent. On helperg.com it is injected by the consent manager after Analytics consent under Google Consent Mode v2.

Can WebmasterID run alongside Google Analytics?

Yes. They are independent. helperg.com runs both, each gated behind the same analytics consent.

Related

What is WebmasterID? · Docs hub · Products · Changelog