Any site you deploy on Vercel can use WebmasterID with the standard consent-gated script tag. This is a normal static/SSR integration — there is no special Vercel partnership 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 set a Content-Security-Policy (via vercel.json headers or your framework), allow the script source and the ingest endpoint:
script-src 'self' https://webmasterid.com;
connect-src 'self' https://webmasterid-ingest-api.vercel.app;
This guide uses the standard script-tag approach; no official marketplace integration is implied.
No — the tracker runs in the browser after consent regardless of rendering mode.
Allow webmasterid.com in script-src and the ingest endpoint in connect-src.
WebmasterID is designed for website visibility you control. Explore the product, docs, and integrations.