Fix duplicate analytics pageviews on Standalone Blazor WebAssembly

Start with the Standalone Blazor WebAssembly installation

For a standalone Blazor WebAssembly application, add the deferred external tracker to the existing host document wwwroot/index.html, once near the end of body. Preserve the Blazor boot script, root element and base address. This guide is specifically for the standalone WebAssembly host document, not every Blazor rendering mode.

Do not insert the global tracker in a route component or HeadContent component. Component removal does not necessarily unload script listeners. Blazor Web Apps, server rendering and enhanced navigation require their own host and lifecycle assessment rather than this standalone installation recipe.

Use the public project key from the DataSag project you are inspecting. A test on a preview domain does not confirm that the production domain has the same code or settings.

Fix duplicate analytics pageviews in Standalone Blazor WebAssembly

1. Inspect the standalone host document and all route components for tracker copies. Keep the global script in wwwroot/index.html rather than inserting it through a component or HeadContent on each route.
2. Inspect JavaScript interop helpers and navigation subscriptions for repeated script loading or a second pageview sender. Component disposal does not necessarily remove listeners registered by an executed global script.
3. Publish and test direct entry, app navigation and Back. Inspect null-name pageviews and later click events for duplication. Confirm the result on the standalone application model instead of inferring behavior for another Blazor render mode.

The standalone app retains one global initialization without component-local scripts or overlapping navigation dispatch.

Complete the collection checks

1. Open Network and filter /api/track. Reload once without clicking or scrolling. Inspect eventName in each payload: null identifies a pageview; scroll, click_heatmap and __datasag_engagement are other records.
2. Count rendered script elements with data-datasag-key. There should be one intended installation for this project. Search your code, site header settings, embeds and tag manager for additional copies.
3. Remove redundant script insertion mechanisms, keeping the site-wide installation. Two copies execute independently even when their browser download is cached.
4. Check for custom router listeners that manually send pageviews. The current tracker handles pushState, replaceState and popstate and ignores a repeated pathname. Do not add a second pageview implementation without a demonstrated gap.
5. Repeat a direct load, a second route and browser Back. Correlate pageview records with actual path changes. A query-only change on the same pathname is not a new pageview in the current tracker.

[...document.querySelectorAll('script[data-datasag-key]')]
  .map(script => ({
    src: script.src,
    key: script.getAttribute('data-datasag-key')
  }));

What a successful check looks like

A single installation and one pageview dispatch for each actual pathname change in the tested sequence. Additional engagement records remain available.

Record the public path you tested, the browser state, the approximate time and the observed request. Check one direct page load and one later navigation so the result covers more than the homepage.

Common mistake

Comparing the total number of events with the number of pageviews produces a false duplicate diagnosis. Keep the event categories separate throughout the check.

Installation snippet for Standalone Blazor WebAssembly

The shared installation belongs in the host document wwwroot/index.html in a standalone WebAssembly app. Use this as the installation reference while checking the procedure above.

<script defer src="https://www.datasag.com/tracker.js" data-datasag-key="YOUR_PUBLIC_KEY"></script>

Related Standalone Blazor WebAssembly guides

• Verify DataSag analytics
• Fix DataSag analytics not working
• Track custom events
• Track UTM campaigns
• Measure AI referral traffic
• Configure CSP for DataSag analytics
• Exclude your own analytics visits
• Load analytics without blocking rendering

Full Standalone Blazor WebAssembly setup guide · Search and AI visibility

References

Official Standalone Blazor WebAssembly documentation covers the integration point. For DataSag data handling, read the privacy policy. Use support if a request fails after these checks.