Why leadmaps?
leadmaps is a hosted analytics platform for teams that want first-party data residency in the EU and a strict tracking-plan workflow, without running their own infrastructure. We run the service in EU-resident infrastructure; you run the SDK and control the data.
What leadmaps optimises for
Section titled “What leadmaps optimises for”EU-resident first-party data. Every event lands in EU infrastructure by default. We are the data processor named in your record of processing activities; no events are forwarded to US-based analytics vendors.
Privacy-positive baseline. Do Not Track is honoured by default, consent is enforced server-side at the ingest endpoint (not by the client), the IP is hashed before it is stored, and the PII filter strips emails and cards from URLs and form events. Cookieless mode is a one-line config switch.
Bundle size. The browser core is under 5 kB gzip and every opt-in module (vitals, errors, clicks, scroll, engaged time, offline queue, retry) is its own subpath that tree-shakes if you don’t import it.
Strict tracking plan. YAML-defined event schemas, validated on ingest, with TypeScript codegen and a CI breaking-change detector. Bad events go to a dead-letter queue you can inspect and replay.
Latency. Ingest is fast (p99 under 5 ms, excluding network). Per-workspace rate limits and monthly quotas keep noisy tenants from starving the rest.
When leadmaps is NOT the right fit
Section titled “When leadmaps is NOT the right fit”You need a heavyweight ad-spend attribution suite. leadmaps focuses on first-party product and marketing analytics. If multi-touch attribution modelling across many paid channels is the core of your workflow, a dedicated attribution tool may suit you better.
You want a private, air-gapped deployment without talking to us. In-VPC and air-gap deployments are available under an Enterprise agreement only. Contact us.
You are not willing to define a tracking plan. leadmaps is opinionated about event quality. The tracking-plan workflow is a feature, not a hurdle, but it does ask you to declare your events up front.
Compared to hosted alternatives
Section titled “Compared to hosted alternatives”| Concern | leadmaps | US-hosted SaaS analytics |
|---|---|---|
| Data residency | EU by default | US (vendor-controlled) |
| First-party requests | Yes (*.leadmaps.nl) | Vendor domain (subject to ad blockers) |
| Bundle size | under 5 kB gzip core | 30 to 80 kB gzip typical |
| Operational overhead | None (we run it) | None (they run it) |
| Pricing model | Per ingested event, Hobby tier free | Per MTU or per event |
What’s stable
Section titled “What’s stable”The public API contract — every SDK export, every HTTP endpoint, every wire field listed under the API reference — is bound by the semver policy. Anything not in that contract is explicitly internal and may change in any release.