# Privacy-First Web Analytics You Own

Move Big Rocks Web Analytics gives product and marketing teams the numbers they actually review—visitors, pageviews, top pages, sources, countries, browsers, and trends—inside the instance they already own. It is a free first-party extension, its source and release path are public, and its data stays in an extension-owned PostgreSQL schema.

## Summary

- Owned visitor data: Events and rollups live in the extension-owned `ext_demandops_web_analytics` schema on your PostgreSQL deployment.
- No per-site license: The public first-party bundle is free to use as a first-party extension; adding another site does not add another Move Big Rocks subscription.
- Privacy by design: The collection path is designed around aggregate operational insight rather than advertising profiles or cross-site identity.
- One operational surface: Analytics review, anomaly triage, knowledge, cases, and follow-up automation can live on the same shared base.

## The dashboard answers the questions small teams ask every week.

This is deliberately focused analytics, not an advertising-data warehouse. It gives teams enough signal to understand acquisition and content performance, spot changes, and decide what to do next.

- Traffic and trends: Review visitors, pageviews, and time-window trends without moving data into a third-party analytics account.
- Pages and sources: See which pages attract attention and which referrers and campaigns are producing it.
- Geography and technology: Use country, browser, device, and operating-system rollups for product and compatibility decisions.
- Shared follow-through: Turn an observation into a case, knowledge update, or automation on the same operational platform instead of leaving it in a dashboard.

## Choose it when ownership and operational simplicity matter more than ad-tech depth.

A separate analytics SaaS can be the right answer when you need a large marketing ecosystem, cross-channel attribution, or an outsourced analytics operation. This extension is strongest when a compact, privacy-conscious team wants reliable first-party insight without another vendor, login, billing plan, identity integration, and data-processing relationship.

- Move Big Rocks Web Analytics [Best for owned operations]: Self-hosted data, public source, no separate product account, and direct connection to the work and knowledge already in Move Big Rocks.
- Privacy-focused analytics SaaS [Best for outsourced convenience]: Usually quicker when you want a standalone hosted dashboard and do not want to operate the underlying database or deployment.
- Large marketing analytics suites [Best for ad-tech ecosystems]: A better fit when advertising attribution, broad third-party integrations, and specialist analyst workflows outweigh data minimisation and platform consolidation.
- Use Move Big Rocks when the goal is trustworthy product and content insight on infrastructure you control.
- Keep a specialist suite when the organisation genuinely uses its specialist capabilities; do not migrate for ideology alone.
- Run both briefly during evaluation and compare the decisions each system actually changes.

## The collection path is inspectable from browser script to owned schema.

Core owns the external route, request limits, and extension lifecycle. The extension owns analytics-specific ingestion, aggregation, and storage. That boundary is visible in the manifest, source, migrations, and threat model.

Proof:
- Source: web-analytics/README.md (https://github.com/MoveBigRocks/extensions/blob/main/web-analytics/README.md) — Documents the extension, supported events, and operating model.
- Contract: web-analytics/manifest.json (https://github.com/MoveBigRocks/extensions/blob/main/web-analytics/manifest.json) — Declares routes, runtime class, scope, storage class, and release identity.
- Implementation: web-analytics/runtime (https://github.com/MoveBigRocks/extensions/blob/main/web-analytics/runtime) — Contains the public ingestion, query, rollup, and dashboard runtime.
- Release: public-bundles.yml (https://github.com/MoveBigRocks/extensions/blob/main/.github/workflows/public-bundles.yml) — Builds, signs, and publishes the first-party bundle and runtime.

## The software price is simple; the operating choice is yours.

The public web analytics bundle has no separate license fee for internal use. On an existing Move Big Rocks instance, its incremental cost is storage, traffic, backups, and the operator time your event volume requires.

- Self-host it [Free first-party bundle]: Install it into your owned instance and operate it with the same deployment, PostgreSQL, monitoring, and backup model as the platform.
- Get rollout help [Scoped professional services]: Ask for help with sizing, migration, validation, dashboards, or production rollout while keeping the instance under your control. (mailto:support@movebigrocks.com?subject=Web%20analytics%20rollout%20help)
- Discuss managed operation [Separate written agreement]: If you want Move Big Rocks operated as a managed service, contact us for a separate commercial agreement; that right is not included in the public source license. (mailto:support@movebigrocks.com?subject=Managed%20Move%20Big%20Rocks)

## Install by signed OCI reference, validate, then activate in a preview workspace.

The extension uses the same explicit lifecycle as every other Move Big Rocks extension. Pin a published version, inspect the declared routes and widgets, validate it against a preview workspace, and only then activate it for real traffic.

- Open the public extension source: Inspect the runtime, migrations, manifest, UI, and tests. https://github.com/MoveBigRocks/extensions/blob/main/web-analytics
- See the real dashboard at full size: Open the production proof image without the page layout. https://movebigrocks.com/static/images/proof/web-analytics-dashboard.png
- Request a live walkthrough: See the live workflow and discuss fit, sizing, and migration. mailto:support@movebigrocks.com?subject=Move%20Big%20Rocks%20web%20analytics%20walkthrough
### Install and verify

Resolve the current version from the public extension catalog before running this sequence.

```text
$ mbr auth login --url https://app.yourdomain.com
$ mbr extensions install ghcr.io/movebigrocks/mbr-ext-web-analytics:VERSION --workspace WORKSPACE_ID --json
$ mbr extensions validate --id EXTENSION_ID --json
$ mbr extensions widgets --workspace WORKSPACE_ID --json
$ mbr extensions activate --id EXTENSION_ID --json
```


## Related

- All extensions: /extensions
- Self-hosting: /docs/self-host
- Security: /security
- License and commercial use: /pricing