API FAQ
Answers to common API integration questions — account_id vs site_id, event-level conversions, JWT scopes, and working /exports/stream examples.
Answers to common API integration questions — account_id vs site_id, event-level conversions, JWT scopes, and working /exports/stream examples.
Sealmetrics uses last-click attribution — the only model that needs no user identification across sessions; UTMs are captured on every hit, no consent needed.
Frequently asked questions about Sealmetrics pricing, billing, and payments.
Why, on our self-assessment, Sealmetrics needs no consent banner for its own analytics (Germany is an open question) — no cookies, nothing stored on the device, a session identifier that rotates daily, and what exactly is recorded on each hit.
Why Sealmetrics numbers differ from GA4 — inflated Direct traffic, entrances instead of persistent-ID sessions, last-click as the only consent-free attribution model, ITP resistance, and why server-side tracking still needs a consent banner.
Answers to the most common questions about Sealmetrics, consentless analytics, attribution, implementation, privacy, product features, and legal compliance.
How to install the Sealmetrics pixel in the head or via Google Tag Manager, add event pixels for conversions and micro-conversions, and verify tracking in Real-Time.
Sealmetrics product FAQ: the 7 reports included (Dashboard, Acquisition, ROAS, Funnels, Pages, Real-Time), customizable funnels, ROAS and API access.
Learn exactly what data Sealmetrics collects, what it does not collect, and how privacy is enforced technically.