DataSag guides · Updated 27 October 2026

Track custom events on Standalone Blazor WebAssembly

Use data-datasag-goal for a click goal, or call window.datasag.track after a completed action. Choose a stable event name and distinguish a click from a successful conversion. 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.

Track custom events in Standalone Blazor WebAssembly

  1. For click intent, add data-datasag-goal to the rendered link or button and let the existing tracker handle it. Keep the global loader in the standalone host document.
  2. For a confirmed C# browser-side action, use a deliberate JavaScript interop helper after the successful result and after the tracker is ready. Do not attempt browser interop during prerendering or use a click goal as proof of server completion.
  3. Test success and rejection in the published app and repeat after navigation. Inspect the named browser payload. If an interop module binds listeners, ensure its lifecycle does not create another listener each time the component is revisited.

The standalone Blazor action emits a browser event only when the tracked outcome and interop readiness are established.

Complete the collection checks

  1. Write the event definition first. For example, signup_click means a visitor pressed a signup link, while signup_completed means your application confirmed account creation.
  2. For click intent, add data-datasag-goal to the element. The tracker delegates clicks, so you do not also need a JavaScript handler for the same goal.
  3. For a completed action, call the JavaScript API in the success handler. Wait for the tracker to be available. An optional guard avoids a crash but intentionally drops the event if the tracker has not loaded.
  4. Send only the context needed for the report, such as a form or plan name. Do not include email addresses, passwords, payment details or freeform form contents.
  5. Complete one successful and one failed attempt. Inspect /api/track for the exact eventName and properties. Only the successful attempt should emit a completed-action event.
  6. Check the event report available to your plan. Collection and access to reports are separate; review current plan details before depending on a particular report.
<!-- Click intent: use this OR your own click handler -->
<a href="/signup" data-datasag-goal="signup_click">Create account</a>

// JavaScript: inside the confirmed-success handler
window.datasag?.track('signup_completed', { form: 'main_signup' });

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.

What a successful check looks like

A controlled successful action produces one event with the agreed name. A validation failure does not emit a success event. Network evidence matches the report definition.

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 goal attribute on a submit button measures clicks, including attempts that fail. Do not report those clicks as completed signups or purchases.

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.