Several sites, one way of reporting.

For teams reporting on websites they do not own.

Multiple sites, properly separated

Each tracked domain is its own site with its own reports, and one snippet can carry several domains. Workspaces are isolated in the database itself by row-level security rather than by a filter in application code — a query without a valid workspace claim returns nothing, and that boundary is covered by its own test suite in CI.

The conversation that gets easier

Explaining a client’s analytics to their legal or procurement team. "Nothing is stored on the visitor’s device, IPs are never written down, and the identifier cannot be recomputed after 48 hours" is a short conversation compared with justifying a tag that shares data onward — and it is a conversation agencies have repeatedly.

Onboarding a client site

Add the domain, paste one script tag. If the client already runs Tag Manager, their existing event tags arrive without re-tagging, which removes the part of the handover that usually needs a developer.

On the list

Team invitations and roles work today. Per-client access scoping inside one workspace, and scheduled or exportable reports, are the two things agencies ask us about most — tell us which one matters to you and we will work to it.