Docs

Servoki developer docs

Everything beyond the basic page view. Pick a trigger and copy the code — every snippet is real, runnable, and uses the same lightweight tracker you already installed.

Not installed yet? Start with the install guide — one script tag and page views start flowing. Then come back here to track the things that matter.

Start here

Set up trackingAdd the script, verify the install and handle single-page apps — page views in about two minutes. API accessUse a Servoki API key to query metrics, manage sites, send server events and export data — full OpenAPI spec and llms.txt.

Track events in the browser

Custom eventsRecord any action — clicks, signups, plays — with servoki.track(). Form submissionsFire an event when a signup, contact or lead form is submitted. Outbound links & downloadsMeasure clicks to external sites and file downloads. Single-page appsCount route changes in React, Vue, Next.js and other SPAs. Tracking across domainsOne visit across your site and its booking engine or checkout on another domain — same snippet, linked in Servoki.

Conversions & revenue

GoalsTurn page views and events into named conversions with revenue. Ecommerce & revenueTrack purchases and attribute revenue to channels and campaigns.

Sharing

Sharing a reportThree kinds of link, and which one exposes data to people without an account.

Server-side

Server events (API)Confirm conversions from your backend — deduplicated, ad-blocker-proof. Meta Conversions APIForward consented conversions to Meta with server-side hashing.

The tracker API, in one place

After the script loads, it exposes a tiny global. Two methods, that's the whole surface:

// record an event (with optional properties)
window.servoki.track('signup');
window.servoki.track('purchase', { plan: 'pro', value: 49 });

// tie this browser to an id you control (for server-side stitching)
window.servoki.setVisitor('anon-abc123');

Setting the visitor id or consent before the first page view

The page view is sent the moment the script runs, so a setVisitor() made afterwards only reaches later events — and the page view lands on a different visitor than your own events. If you use setVisitor() or a consent banner, add this one-line stub before the Servoki script tag and make your calls through it. They are queued and applied before the first page view; queued track calls are sent right after it.

<script>window.servoki=window.servoki||function(){(servoki.q=servoki.q||[]).push(arguments)};</script>
<script defer data-site="example.com" src="https://servoki.com/tracker.js"></script>
<script>
  servoki('setVisitor', 'anon-abc123');   // same id you send with server events
  servoki('consent', true);                // if your banner already has consent
  servoki('track', 'view_item', { sku: 'A1' });
</script>

The command form keeps working after the script has loaded, so the same calls are safe at any point in the page’s life.

Page views fire automatically on load. Everything else is a track() call you place where the action happens. The tracker sets no cookies and respects Do Not Track.

Start hereCustom events → Server-sideServer events API →