Features
Two jobs. One platform. Zero cookies.
Everything below ships in every Servoki workspace — the analytics front measures, the convert front forwards. Both are first-party and consent-aware by design.
Analytics front
Real-time, cookieless analytics
A live event stream and active-visitor view that updates second by second — pageviews, custom events, engaged time, referrers, UTM campaigns, countries, browsers and operating systems. No sampling, no day-old reports.
Identification is done with salted BLAKE3 hashes that rotate every 24 hours: good enough to count unique visitors accurately, useless for building profiles. That's why the analytics front needs no cookie banner for measurement in most setups.
pageviews · custom events · engaged time · UTM · geo · browser · OS · bot filtering
Analytics front
Funnels and goals that carry revenue
Define multi-step funnels and conversion goals, and see not just drop-off percentages but the revenue attached to every stage. A funnel that ends in a server-confirmed payment shows you real money, not proxy metrics.
Goals can match pages or custom events, and every funnel stage can break down by source, campaign or country — so "where do paying customers actually come from" is one click, not a spreadsheet afternoon.
Analytics front
Revenue attribution
Every conversion carries its value, currency and the visitor's first- and last-touch context: referrer, UTM campaign, landing page. Servoki rolls that up into per-channel and per-campaign revenue so you can compare what Google, Meta, newsletters and organic actually return — measured by your own first-party data rather than each platform's self-graded homework.
Convert front
Server-side events with deduplication
Browsers lie: scripts get blocked, tabs close mid-purchase, pixels fire twice. Servoki's server event API lets your backend confirm what really happened — a paid order, a verified signup — with an event_id that deduplicates against anything the browser already reported.
The result is one clean conversion record per real conversion: browser context when available, server truth always.
Convert front
Consent-gated Meta Conversions API
Forward server-confirmed conversions to Meta's Conversions API so your campaigns optimise on real purchases — but only for visitors who consented. Identifiers are hashed server-side before they leave, forwarding is deduplicated against the pixel, and every consent decision is recorded in an append-only log for your audit trail.
This is the part most privacy tools refuse to touch and most server-side tag managers do without asking. Servoki's position: forward everything you're allowed to, nothing you're not.
Privacy layer
PII shield and daily salt rotation
Personal data shouldn't reach your analytics database in the first place. Servoki auto-detects likely PII in URLs and event properties — emails, phone numbers, tokens — and masks it before storage, with custom masking rules for anything specific to your stack.
Visitor identity is a salted hash whose salt rotates daily and is then purged: yesterday's identifiers cannot be linked to today's, by anyone, including us.
BLAKE3 hashing · 24 h salt rotation · PII auto-detection · masking rules · no raw IP storage
Analytics front
Anomaly alerts and an insights digest
Servoki watches your own baselines — traffic, conversion rate, revenue per day — and tells you when something breaks pattern: a landing page that suddenly converts half as well, a referrer that triples overnight, a checkout error eating revenue. A periodic insights digest summarises what changed and why it might matter, so the dashboard works for you even when you're not looking at it.
Also included:
- Public shareable dashboards for clients and teammates
- Data export — CSV, NDJSON and Parquet, your data is yours
- Conversion webhooks with HMAC signing
- Workspaces, organizations, members and API keys
- Custom domains for first-party collection
See your real numbers for the first time
Early access is rolling out in waves — join the waitlist and we'll hold your spot.