DataSag guides · Updated 27 October 2026

Fix DataSag analytics not working on Angular

Find the first missing step in the delivery chain: published HTML, executing tracker, tracking request, successful response and project report. Changing several settings at once makes the failure harder to identify. This guide applies to Angular.

Start with the Angular installation

Inspect the Angular workspace project configuration to identify its index document, commonly src/index.html. Add the deferred external script once to the existing head and preserve the root element and build-managed assets. Build the intended application project and inspect its deployed output rather than a library package.

A workspace can contain several applications with different index files and build targets. Component templates and services should not repeatedly insert the global loader. For server rendering, keep browser API calls out of server execution.

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 Angular

  1. Inspect the Angular build target and deployed index document first. Multi-application workspaces can build another project, leaving your edited src/index.html unused in the published output.
  2. Check a direct nested URL for a hosting fallback error. Then inspect the real script key and browser policy errors. A tracker absent from the served document cannot be repaired by a component service call.
  3. For missing action events, trace the browser subscription or success handler. SSR and prerender execution cannot call the visitor window. Also check whether the router changes only a fragment while your expected report groups by pathname.

The diagnosis separates wrong build input, deep-link serving, browser execution and unsupported navigation assumptions.

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 Angular

The shared installation belongs in the head of the application index document selected by the build configuration. 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 Angular guides

Full Angular setup guide · Search and AI visibility

References

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