DataSag guides · Updated 27 October 2026
Install DataSag on Standalone Blazor WebAssembly
Add DataSag to Standalone Blazor WebAssembly through the host document wwwroot/index.html in a standalone WebAssembly app. Create a project first, then replace the example public key with the key from your dashboard.
Where to put the tracking script
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.
<script defer src="https://www.datasag.com/tracker.js" data-datasag-key="YOUR_PUBLIC_KEY"></script>The project tracking key is public and belongs in this snippet. Account credentials, provider API keys and database secrets do not. Keep your existing consent choices and only load analytics when your site's policy permits it.
Verify the published installation
- Publish the change to the domain visitors actually use. Open a nested page as well as the homepage.
- In browser developer tools, find one tracker.js script with the correct data-datasag-key value.
- Filter Network requests for /api/track. Confirm that a pageview payload names the path you opened and receives a successful response.
- Open the same DataSag project and choose a date range containing your test. Confirm the page appears before measuring campaigns or conversions.
Avoid this Standalone Blazor WebAssembly setup mistake
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.
Keep pageviews separate from scroll, click and engagement events. A page can generate several tracking requests while still representing one visit to that path.
Events and conversions
Use a goal attribute on rendered markup for a click. For a confirmed C# browser-side action, use a deliberate JavaScript interop helper only when the browser and tracker are ready. Prerendering cannot safely make the same browser call.
<a href="/signup" data-datasag-goal="signup_click">Create account</a>This attribute measures a click. To record a completed signup, call window.datasag.track in the application's confirmed success handler. Current plan details determine which event and campaign reports are available.
Setup and troubleshooting recipes
- Verify DataSag analytics on Standalone Blazor WebAssembly
Check the rendered script, public project key, browser requests and first pageview before relying on your analytics.
- Fix DataSag analytics not working on Standalone Blazor WebAssembly
Trace missing website visits through script placement, project keys, exclusions, consent, network delivery and report filters.
- Fix duplicate analytics pageviews on Standalone Blazor WebAssembly
Separate legitimate engagement events from duplicate tracker installations and repeated pageview dispatches.
- Track custom events on Standalone Blazor WebAssembly
Add click goals or completed-action events with DataSag's data attribute and browser JavaScript API.
- Track UTM campaigns on your website
Create consistent tagged links and verify that campaign parameters reach your website and DataSag.
- Measure AI referral traffic on your website
Check visits with observable AI referrers and understand the difference between traffic, citations and LLM visibility.
- Configure CSP for DataSag analytics on your website
Diagnose blocked scripts, beacon requests and image fallbacks without disabling your site's Content Security Policy.
- Exclude your own analytics visits on your website
Use DataSag's browser exclusion switch to keep your testing activity out of future tracked visits.
- Load analytics without blocking rendering on Standalone Blazor WebAssembly
Choose a non-blocking script placement and verify actual loading behavior instead of relying on a fixed speed claim.
Platform reference
Official Standalone Blazor WebAssembly documentation explains the platform integration point. DataSag-specific behavior here follows the current tracker and project setup.
Need a different stack? Browse every installation guide.