Sites on Cloudflare Pages or behind the Cloudflare CDN use WebmasterID with the standard consent-gated script tag. No Cloudflare app or partnership is required.
For GDPR/ePrivacy, load the tracker only after analytics consent. The pattern below is the same consent-gated approach documented in Privacy & GDPR — inject it from your consent manager when the analytics category is granted, not unconditionally.
<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>
If you add a CSP via Cloudflare Transform Rules or your origin, allow https://webmasterid.com in script-src and the ingest endpoint in connect-src.
The tracker script is static and cacheable. Avoid caching consent state; the consent manager runs per-visitor in the browser.
No — this is a standard script-tag integration; no official app/partnership implied.
No. Allow the script and endpoint in CSP and it works behind the CDN.
No. It is client-side; Workers are optional and not needed.
WebmasterID is designed for website visibility you control. Explore the product, docs, and integrations.