Six workspaces. Twelve modules. One console.

Pageviews, sessions, sources, UTM and ad click ids, geo and devices, plus every custom event you fire — written to one partitioned table and resolved to one person. Funnels, retention, goals, a live view and a raw event explorer read from it.

Events are partitioned by month and indexed by application, environment and time, so a thirty-day breakdown is a range scan rather than a full table read. Sessions close after thirty minutes of inactivity or on $session_end, bounce and duration are derived from them, and daily rollups keep the dashboards fast without discarding the raw events behind them — every chart can still open the feed that produced it.

Read-only connectors to Stripe, Polar or RevenueCat, normalized into subscriptions, payments and a daily MRR movement series, with customers linked to the person record by your own user id, or by email when the provider carries none. SaaS Pro Max never charges anything — it only reads.

Webhooks are signature-verified per provider and an hourly backfill catches anything a webhook missed. Amounts are stored in minor units with their currency, MRR is normalized across intervals, and the daily series separates new, expansion, contraction and churn so a flat MRR line still tells you what happened underneath it.

identify() merges the anonymous visitor into a person, keeping the earliest first-touch attribution and re-pointing their past events. Profiles carry traits, lifecycle stage, tags, notes and segments, and personal fields stay hidden unless the role carries permission to read personal data.

Identity resolution is explicit: identify() moves the anonymous person's identities onto the distinct person, sums the counters, keeps the earliest first-seen date and first-touch attribution, and re-points the last ninety days of events and sessions. alias() links a second id to the same person. Nothing is guessed from an IP, because the IP is a hash.

The SDKs capture uncaught errors, unhandled rejections, React error boundaries and framework request errors, parse the stack, mark in-app frames and attach breadcrumbs. Issues carry a release, a status and the people affected — which is a link back to the person, not a number.

Grouping is by fingerprint, and you can set the fingerprint yourself when the default grouping is wrong. Frames are marked in-app or vendor so the culprit line is the one you wrote, breadcrumbs carry the navigation, clicks, requests and console lines that preceded the throw, and an issue moves between unresolved, investigating, resolved and ignored with the change recorded in the audit ledger.

Percentage rollouts and property rules, evaluated in the browser from a cached payload and on the server through the same endpoint. Both use the shared hash, so a person bucketed on in the browser is bucketed on in your API too.

The browser SDK loads a flag payload once and re-evaluates locally, so a flag check is not a network call; the server evaluates through POST /api/v1/flags/evaluate. Both use rolloutBucket from @saaspro/shared, whose reference vectors are pinned in that package's tests — the same person cannot land in different buckets on the two sides of your app.

Map one of your events onto an ad platform's event once, and every matching event is dispatched from the worker with retries and a delivery record. Click ids captured at landing (gclid, fbclid, ttclid, li_fat_id) ride along.

Every dispatch writes a delivery row with a redacted request, the response and the error, so a conversion that did not arrive has an answer rather than a shrug. Deduplication uses the SaaS Pro Max event id as the destination's event id, which is what lets a browser pixel and a server-side conversion describe the same purchase without counting it twice.