Traffic reports
Visitors and page views over time, plus pages, referrers, campaigns, countries, devices, browsers, and operating systems.
Your site's traffic, right inside Umbraco.
Web Analytics reads the traffic your site already sends to Vercel or Plausible and reports it in the backoffice. Editors see the site-wide numbers and how the page they're editing is doing, without leaving Umbraco.
dotnet add package TheBuilder.WebAnalyticsUmbraco CMS 17.1 through 18.x
Nothing new on your public site. Web Analytics only reads. Tracking on your site stays exactly as you set it up, and the token never leaves server-side configuration.
Bring your own provider
Point it at a Vercel project or a Plausible site. Where a provider can't report something, the backoffice hides that panel instead of showing an error.
Vercel Web Analytics
Connect a Vercel project with a scoped access token. Visitors, page views, pages, campaigns, custom events, and feature flags, with the token never stored in Umbraco.
ReferencePlausible
Point at Plausible Cloud or a self-hosted instance with a Stats API key. Adds global event filtering and custom event properties on top of the core reports.
ReferenceWhat's in the dashboard
One dashboard per connection, and the same reports again on any document you map.
Document context
An Analytics view inside a published document's workspace, filtered to that document's route. Toggle child paths to cover the whole section.
Compare and filter
Each metric shows how it moved against the period before it. Turn any breakdown row into a filter across the whole dashboard.
Multi-site support
Connect several Vercel projects and Plausible sites to one Umbraco installation and switch between them.
Private credentials
Tokens live in server-side configuration. They are never written to Umbraco and never sent to the browser.
No tracking changes
Reads the data your provider already collects. It never installs, replaces, or configures tracking on your public site.
Page performance, next to the content
Map a document root and every published document below it gains an Analytics workspace, filtered to its own route. It follows Umbraco's Content permissions, so an editor who can browse a page can read its numbers without access to the global Analytics section.
Read the guide
Connected in three steps
All three steps, and what to check afterwards, are on the quickstart page.
Install the package
Add TheBuilder.WebAnalytics to your Umbraco web project. Services and backoffice extensions register automatically.
Configure a credential
Store a read-only Vercel or Plausible credential in server-side secret configuration.
Connect and test
Add a connection at Settings → Web Analytics, run Test connection, and open the Analytics dashboard.
Put the numbers where the content is
Install the package, point it at your Vercel project or Plausible site, and editors get their traffic reports without a second login.
More from TheBuilder
Focused packages for modern Umbraco projects.
Blur Placeholder
Generates a WebP, BlurHash or ThumbHash placeholder when an image is saved, ready for your frontend to show while the image loads.
AI Image Disclosure
Reads the C2PA Content Credentials on uploaded images and flags the ones that say they were made or edited with AI.
App Translations
Lets editors change the next-intl or i18next messages in your app from Umbraco. Your app fetches the changes when it runs.
API OIDC
Lets frontends call the Delivery API and your own endpoints with an OIDC token from their hosting platform, instead of a shared API key.
Schema City
Shows your Document Types as a city in the backoffice, with the links between them, and flags schema problems before they ship.
Delivery API Inspector
Adds an API tab to every document and media item in the backoffice, with the JSON the Delivery API returns for it.
Umbraco Rich Text
Renders the rich text JSON from the Umbraco Content Delivery API with React. You decide how each block and node is rendered.