Who is the Agency plan for?

Agencies, freelancers, and in-house teams running more than one site at a time. Also founders with a small portfolio (3–25 sites) who want one analytics fabric instead of one Plausible per project. Agency unlocks multi-workspace, team membership with RBAC, the Event Explorer, exports, audit logs, and the MCP + Agent integrations.

How is multi-site organised?

Sites belong to workspaces; users belong to workspaces via membership. Agency unlocks multiple workspaces per account so you can give each client their own fabric without sharing data across them. RBAC roles (owner / admin / operator / analyst / support / readonly) refine permissions inside each workspace.

Can a team member only see one client's sites?

Yes. Workspace membership is the access boundary. Add a team member to one workspace and they see only that workspace's sites, events, and attribution. Suspended or revoked memberships lose visibility immediately.

How does the audit log help on the agency side?

Every admin action (member invited, role changed, repo mapping verified, MCP key generated, export run) is recorded in the workspace's append-only audit log. PII is sanitised; the trail is immutable. Downstream compliance and client conversations get a real answer instead of guesswork.

Does Claude / MCP work across many client workspaces?

MCP is workspace-scoped. One Bearer key reads one workspace. For an agency with many clients, run one MCP key per client workspace; Claude can switch between them. Cross-workspace reads remain impossible.

How do client invites work?

Invite team members by email. The invite token is single-use, SHA-256-hashed, and expires in 7 days. The email is sent via AWS SES from the agency-managed sender. Roles are workspace-scoped, so the invited user lands in exactly the workspace and role you intended.

Agency analytics

One analytics fabric across many clients — without leaking data across them

WebmasterID Agency is built for operators with more than one site to look after. Multi-workspace, RBAC team membership, the Event Explorer, exports, audit logs, and Claude/MCP integration. AI-native by design, agency-ready by default.

Upgrade to Agency Compare plans Talk to us

Use cases

What agency analytics is for

The day-to-day shape of running many sites without giving up the integrity of any one of them.

One workspace per client

Each client gets their own data fabric. Sites, events, attribution, and exports are workspace-scoped. Cross-workspace reads are impossible.

Add a team member to one client

Workspace membership is the access boundary. Add an operator to one client's workspace; they see that workspace and nothing else.

Brief the agency every morning

The Agent's daily operator brief deduplicates findings across sites within a workspace. The same finding on many sites collapses into one recommendation.

Build the weekly client report

Filter the Event Explorer to a client, export CSV or NDJSON, drop into the report. The filter set is the report definition.

Investigate across the portfolio with Claude

MCP is workspace-scoped. One Bearer key, one prompt: 'which client sites lost AI traffic this week' returns the cross-section.

Hand work back to the client

Invite the client as a readonly member of their workspace. They see what you see, with the same audit trail.

How WebmasterID helps

Built for the portfolio shape from day one

Running multiple sites in 2026 used to mean running multiple analytics dashboards. With AI assistants entering the workflow, single-site tools start to feel limiting. WebmasterID is built for the agency shape.

Multi-workspace

Each client gets their own workspace. Sites, events, attribution, and exports are workspace-scoped. Cross-workspace reads are impossible by construction.

RBAC team membership

Unlimited team members across workspaces. Roles: owner / admin / operator / analyst / support / readonly. Permissions are workspace-scoped.

Event Explorer

Investigation surface across the workspace's full event stream. Filter by date, type, country, pathname, referrer, session, visitor, or campaign.

Exports without per-export gating

CSV + NDJSON exports of filtered slices. Drop into client reports, warehouses, or reconciliation. Audit log records each export.

Append-only audit log

Every admin action recorded. PII sanitised, trail immutable. The compliance conversation has a real answer.

Workspace-scoped MCP

One Bearer key per workspace; Claude reads the workspace through MCP. Read-only by construction; the operator decides what changes.

Feature

Agency-ready features in plain terms

No fake automation, no fake autonomy, no fake customer numbers. The honest shape of agency analytics with WebmasterID.

Daily operator brief

Per-workspace daily brief that ranks top actions for the day. Duplicates across sites are deduplicated so the brief stays readable.

Per-site repo mappings

Each site can map to its own repository so AI-assisted code prep stays scoped to the right codebase. Operator approval per change.

Per-client invite flow

Invite tokens are single-use, SHA-256-hashed, expire in 7 days. Email sent via AWS SES. The invited member lands in the workspace and role you set.

No surprise charges

Transparent plan pricing on /pricing. Agency is one plan, not a hidden bundle. Custom infrastructure is a separate Business conversation.

Privacy & trust

An agency-grade privacy posture, by default

Agencies hold data on behalf of clients. WebmasterID is built so the data each agency holds is as small as the job requires.

No cookies, no fingerprinting
The tracker stays small. Clients can disclose analytics in their own privacy notice without surveillance-grade caveats.
No raw IP storage
IPs are anonymised at the edge. Raw IPs never reach the database.
No data sale or sharing
Workspace data stays in the workspace. We never sell, share, or license it to third parties.
GDPR-aligned by design
Minimal data, anonymised at the edge, no cross-site identifiers. The data-processing page has a controller / processor overview for clients.

For a custom infrastructure conversation, write to info@helperg.com. See also /privacy-policy and /data-processing.

FAQ

Agency analytics, answered

Who is the Agency plan for?: Agencies, freelancers, and in-house teams running more than one site at a time. Also founders with a small portfolio (3–25 sites) who want one analytics fabric instead of one Plausible per project. Agency unlocks multi-workspace, team membership with RBAC, the Event Explorer, exports, audit logs, and the MCP + Agent integrations.
How is multi-site organised?: Sites belong to workspaces; users belong to workspaces via membership. Agency unlocks multiple workspaces per account so you can give each client their own fabric without sharing data across them. RBAC roles (owner / admin / operator / analyst / support / readonly) refine permissions inside each workspace.
Can a team member only see one client's sites?: Yes. Workspace membership is the access boundary. Add a team member to one workspace and they see only that workspace's sites, events, and attribution. Suspended or revoked memberships lose visibility immediately.
How does the audit log help on the agency side?: Every admin action (member invited, role changed, repo mapping verified, MCP key generated, export run) is recorded in the workspace's append-only audit log. PII is sanitised; the trail is immutable. Downstream compliance and client conversations get a real answer instead of guesswork.
Does Claude / MCP work across many client workspaces?: MCP is workspace-scoped. One Bearer key reads one workspace. For an agency with many clients, run one MCP key per client workspace; Claude can switch between them. Cross-workspace reads remain impossible.
How do client invites work?: Invite team members by email. The invite token is single-use, SHA-256-hashed, and expires in 7 days. The email is sent via AWS SES from the agency-managed sender. Roles are workspace-scoped, so the invited user lands in exactly the workspace and role you intended.

Related cluster pages

The agency story sits next to the multi-site and AI-assisted stories.

Multi-site analytics

The data spine the agency analytics page sits on.

AI-assisted analytics

The AI-assisted workflow shape agencies use for investigation.

Attribution analytics

Directional attribution across clients, with confidence labels.

AI visibility analytics

AI-side coverage signal across client sites.

Event Explorer

The investigation surface for client report-building.

Pricing

See what Agency unlocks today.