View and troubleshoot analytics for a site
Each site in Hub has its own **Analytics** tab, scoped to that site's analytics source. Overview, Conversions, Events and Troubleshooting are all available within the same site workspace without switching to workspace-wide reporting. ## Open site analytics 1. Open **Sites** in your workspace. 2. Select the site you want to review. 3. Select the **Analytics** tab. The analytics panel loads the source linked to this site automatically. If no source is linked, the panel prompts you to connect one in **Settings → Connections**. ## Analytics views The Analytics tab is divided into four views, accessed using the navigation at the top of the panel: | View | What it shows | |---|---| | **Overview** | Visitors, page views, sessions, conversion totals and trend charts for the selected date range. | | **Conversions** | Conversion rules and funnel performance. | | **Events** | Individual tracked events, including page views and custom-tracked actions. | | **Troubleshooting** | Diagnostics for the linked analytics source and tracker configuration. | ## Site Home dashboard summary The **Home** tab for each site shows a compact traffic summary — daily visitors, page views and sessions for the last 30 days — alongside the analytics connection status. Select **Analytics** from the Home tab to open the full per-site panel. ## Analytics source scoping The Analytics tab matches your site to its analytics source by the exact site ID, preventing similarly named or unrelated sources from being selected. A source is only shown when it is active and not archived. Collection status shows one of three states: - **Paused** — the source exists but tracking is disabled. - **Awaiting first visit** — the source is enabled but has not yet received any events. - **Recent data** / **No recent data** — based on the last event received within the past 24 hours. ## Analytics settings are live Analytics settings (enabled state and measurement key) are not frozen into a version snapshot. Enabling tracking or rotating the measurement key takes effect on the public site immediately — you do not need to republish your site content. ## Troubleshoot missing visits Select the **Troubleshooting** view to diagnose why visits may not be appearing. ### Check live configuration Select **Check live configuration** to inspect the published site's tracking settings: - Whether the site is published. - Whether the linked source is enabled on the live site. - Whether the source ID and measurement key match. ### Check allowed origins Paste the visitor URL into the **Visitor URL** field to check whether that origin is allowed to send analytics. The troubleshooter distinguishes: - **Allowed** — the origin is listed in the source's allowed origins. - **Blocked** — the origin is not listed. Add its exact HTTPS origin in **Connections**, including `www` if used. - **Invalid** — the URL must be a complete HTTP or HTTPS address. ### Test a real visitor session The Troubleshooting panel includes a step-by-step guide: 1. Open the published website in a private browser window. Signed-in editors and draft previews are excluded from analytics. 2. Allow analytics in the website's consent popup. A rejected choice, Do Not Track, or Global Privacy Control prevents collection. 3. Visit a second page and wait a few seconds, then return to Hub and check Events and the last activity time. 4. If nothing arrives, inspect the Network panel in the visitor's browser: `analytics.js` must load, and `/analytics/collect` requests should succeed. A 403 means the origin is blocked; 404 means a disabled source or mismatched key; 429 means rate limiting. Browser extensions may also block requests. ### Hub admin paths in event history If older events show Hub admin paths (for example `/o/org/hub/`), this is a known behaviour from earlier tracker versions that remained active after navigating away from a public site. The updated tracker stops automatically on exit. Historical events are not modified. ## Tracker lifecycle The analytics tracker for workspace-hosted sites is constrained to its public route. When a visitor navigates from the public site into a Hub admin path, the tracker stops automatically — removing its listeners, timers and API registration — so Hub admin page views are not recorded as site visits. If you remount the tracker (for example, by navigating back to the public site), it restarts cleanly without stacking duplicate history hooks. ## Navigation and browser history Analytics links from site connections retain the selected site in the URL, so browser history and filter changes stay consistent as you navigate. ## Connect a source If no analytics source is linked to your site, select **Set up** or go to **Settings → Connections → Analytics** to connect one. Once connected, return to the site's Analytics tab to view reporting scoped to that site.