Setup
1
Turn on pageview tracking
Automatic pageviews are off by default. Set Call
trackPageviews: 'auto' to collect aggregate pageviews while consent is pending and full pageviews after consent. Pass the visitor’s current consent choice on every load.Wendung.setConsent('granted') or Wendung.setConsent('denied') from your consent manager. If you want to wait for consent before collecting anything, use trackPageviews: true. See the consent guide for saving and restoring the choice.The SDK observes pushState, replaceState, and popstate. Aggregate collection ignores changes to only the query string or fragment.If your router changes the URL without touching the history API, call page() yourself after each navigation. It records a pageview for the current URL.Pageviews count against your plan’s monthly pageview allowance, separate from events. The free plan has no allowance, so web analytics is available on paid plans only. See Plans and limits.
2
Register the site
Pageviews are stored per project, but the reports are per hostname. Open Sites in the sidebar and click Add site. The hostname picker lists your project’s allowed origins; pick the one you want to report on.If you deploy the same app on several hostnames, register each one. The All sites row on the Sites page combines them.
3
Clean up paths
Open the site’s settings to add path rules and a query parameter allowlist. Built-in rules already collapse numeric IDs and UUIDs to
:id and :uuid; add your own for anything else that fragments a page, such as slugs or short codes.Paste a real URL into Preview to see the normalized result before you save. Rules affect pageviews collected from then on. See Pageviews and sessions for how matching works.4
Read the site dashboard
Click the site to open it. The metric rail shows unique visitors, pageviews, sessions, views per session, bounce rate, and session duration; click any of them to chart it. The panels below rank pages, sources, locations, and devices. Click a row to filter the whole page by that value, and hover a row for copy and filter actions.Pageviews include aggregate and consented traffic. Visitors, sessions, engagement metrics, and the current-visitors badge cover consented traffic only. Aggregate pageviews do not create visitors or sessions. See metric coverage.
5
Tag campaign links
To see where a campaign’s traffic goes, add the standard parameters to the links you send out. The ingest endpoint reads them from full pageviews. Aggregate pageviews omit query parameters, so they cannot carry campaign tags.The visits show up under Sources → Campaigns, split by campaign, UTM source, or UTM medium, and each value is a filter. See campaign parameters for what is captured.
6
Pin sites to the Overview
Open Overview and switch to the Web tab. It shows the All sites card and one card per pinned site, each with a 24-hour sparkline and a visitor count. Use the + card to pin more sites, and the card menu to unpin them. The Overview remembers which tab you looked at last.
7
Add web blocks to a dashboard
Dashboards have three web block types: Web summary, Web trend, and Web breakdown. Each block can be scoped to one site or to all sites, and each has its own period. Shared dashboards include them.
Filtering
Every panel row is a filter. Clicking/pricing in Top pages filters the report to that path; clicking again removes the filter. The filter bar accepts is and is not for every dimension, so “Country is not United States” is one click away from the row action. Filters and the date range are part of the URL, so a filtered view can be shared as a link.
What’s next
Pageviews and sessions
What each pageview carries and how sessions and normalized paths are derived.
Site details
Every panel and control on the site dashboard.