Separate site truth from portfolio truth

Each site needs its own timezone, currency, internal filters, consent behavior, goals, and access boundary. A portfolio view should roll up only metrics with shared definitions. Adding “users” from tools with different identity windows or adding revenue in several currencies creates a confident but incoherent total.

Define a portable core schema: pageview, qualified outcome, source taxonomy, campaign convention, implementation state, and data-quality status. Let individual sites add local events without polluting the portfolio layer. Version the schema and annotate migrations.

Design permissions before invitations

Decide who owns the analytics property, collection domain, billing account, raw export, and recovery method. Use role-based access, client-specific groups, single sign-on where appropriate, and a recurring access review. Shared credentials and one universal dashboard link are not a client-access strategy.

Offboarding should remove access without deleting evidence the client owns. Document export formats, retention after cancellation, property transfer, and the handling of agency-created annotations or calculated metrics. Test the exit path before it becomes urgent.

Forecast the real cost curve

Vendors price by pageviews, events, sites, seats, features, retention, or combinations of those dimensions. Model the median month, peak month, growth, custom events that count as usage, additional site packs, and required support. Include the labor needed for hosting, upgrades, backups, and security when comparing self-hosted software.

Clicky, Matomo, Plausible, and Fathom expose materially different plan structures and detail levels. Recheck official pricing on purchase day. A portfolio with many quiet sites may favor generous site allowances, while one high-traffic property may make event tiers dominant.

Operate collection health at portfolio scale

Maintain a registry of domain, owner, property ID, script version, consent integration, verified outcome, last event time, and last manual audit. A green synthetic check should traverse the same edge and collection path as real traffic while remaining excluded from reports.

Alert on missing data, sudden schema shifts, unexpected hostnames, duplicate pageviews, and consent-state anomalies. Pair each dashboard row with data freshness and implementation status. Multi-site reporting becomes trustworthy when a quiet chart can be distinguished from a broken tag.

Direct answers

Questions this guide answers

What should a multi-site analytics tool include?

Look for site isolation, portfolio roll-ups, granular roles, shared definitions, implementation health, exports, predictable pricing, and an ownership transfer path.

Can visitor totals be added across sites?

Only when identity methods, date windows, filters, and definitions align; even then, the same person may appear on several sites.

Is self-hosted analytics cheaper for many sites?

The license may be, but infrastructure, upgrades, backups, security, support, and staff time must be included in the comparison.

Evidence

Primary-source ledger

  1. Clicky plans and site allowancesClicky · accessed 30 July 2026
  2. Fathom pricing and site allowancesFathom Analytics · accessed 30 July 2026
  3. Matomo cloud and on-premise plansMatomo · accessed 30 July 2026

Scope note: Vendor plans, allowances, and features change. Verify official terms and calculate operational labor before making a portfolio purchasing decision.

Found an outdated fact or a material omission?Read the corrections and recheck policy.