DataSag guides · Updated 27 October 2026

Verify DataSag analytics on Standalone Blazor WebAssembly

A script tag alone does not confirm that analytics works. Verify the published document, the request to DataSag and the matching visit in the correct project. This guide applies to 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.

Verify DataSag analytics in Standalone Blazor WebAssembly

  1. Confirm the project is standalone Blazor WebAssembly and inspect its physical wwwroot/index.html host. Add the tracker once near the end of body while preserving the base address, root element and Blazor boot script.
  2. Publish the application and open a nested route directly on its public host. Check the browser receives the application document, downloads the tracker and sends a pageview for the intended pathname.
  3. Use the app NavigationManager-driven navigation and Back, then inspect requests. Keep this result scoped to the standalone host. Do not apply it unchanged to a Blazor Web App using different render modes or enhanced navigation.

The standalone WebAssembly host records the verified entry and navigation sequence from one physical document installation.

Complete the collection checks

  1. Open the published website in a normal browser window with the Network panel recording. Use a browser profile where you can control extensions and your consent choice.
  2. Filter network requests for tracker.js. Confirm it returns JavaScript successfully and that the rendered script has the project's data-datasag-key attribute. The example YOUR_PUBLIC_KEY must be replaced.
  3. Filter for /api/track and reload once. Inspect a request with eventName null or absent. Its projectKey and path should match the chosen project and the page you opened.
  4. Open that DataSag project, choose a date range containing today and inspect the matching path. Use the configured report timezone when checking dates.
  5. Navigate to a second path, then use Back. Compare pageview requests with the route changes rather than counting every request as a pageview.
document.querySelectorAll('script[data-datasag-key]').length
// Expected: 1

document.querySelector('script[data-datasag-key]')?.getAttribute('data-datasag-key')
// Expected: your project's public key

typeof window.datasag?.track
// Expected after the script runs: 'function'

What a successful check looks like

One rendered tracker installation, a successful request for the intended page and a corresponding entry in the intended project. Scroll and engagement requests are separate event types.

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

A successful tracker.js download only proves that a file loaded. It does not validate the project key, consent state or tracking endpoint. Test a real published path before declaring setup complete.

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

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.