Fix DataSag analytics not working 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 DataSag analytics not working in Standalone Blazor WebAssembly

1. Identify the Blazor application model before editing files. A standalone WebAssembly wwwroot/index.html recipe does not identify the host document for every server-rendered Blazor Web App.
2. For the standalone app, inspect the deployed host document and public base address. A direct nested-path hosting error can prevent the app and tracker from loading before any C# component runs.
3. If pageviews work but an action event fails, inspect browser readiness and JavaScript interop timing. Do not make the same window call during prerendering or assume removing a component unloads scripts it previously executed.

The failure is traced to application model, served host document or browser interop readiness rather than arbitrary component script insertion.

Complete the collection checks

1. Confirm the change reached the public domain. Inspect the live HTML and clear only caches that serve the old document. A saved editor change may still need publishing.
2. Check that tracker.js exists in the Network panel and that the script contains the public key from the same DataSag project you are viewing.
3. Check whether your test browser is excluded with datasag_ignore. Restore inclusion with ?datasag_ignore=false only if this browser should count. Respect any consent controls configured on your site.
4. Inspect the browser Console for Content Security Policy or script errors. Check /api/track request responses: 400 indicates invalid input, 404 can indicate an unknown project key, and a server failure needs investigation rather than repeated snippet changes.
5. Try a controlled browser profile to identify an extension block. Do not bypass a visitor's privacy preferences. Then check the project's selected date range, path and domain.
6. Collect the affected public URL, approximate time, request status and installation location for support. Omit account credentials and visitor data from screenshots.

typeof window.datasag?.track
// If undefined, first investigate whether the script executed.

new URL(location.href).searchParams.get('datasag_ignore')
// Also check for a previously saved browser exclusion.

What a successful check looks like

The first failed boundary is identified and corrected, and a new controlled visit reaches the right project. The browser Console and Network panel provide the evidence.

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

Do not replace the public project key with a Supabase, Stripe or provider secret. The browser snippet uses only the project's public tracking key.

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 duplicate analytics pageviews
• 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.