DataSag guides · Updated 27 October 2026

Fix DataSag analytics not working on Hugo

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 Hugo.

Start with the Hugo installation

Add the deferred external script to the shared HTML head partial used by your Hugo theme, or to its applicable base template. Use a project override rather than editing a downloaded theme in place. Preserve Hugo template blocks, partial calls and existing head content, then rebuild and publish the generated files.

Hugo template lookup can select different templates by section, content type, language or output format. A theme may have a documented custom-head extension point. Inspect the rendered HTML for each intended page kind instead of assuming one partial covers all outputs.

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 Hugo

  1. Inspect the affected generated HTML and trace the Hugo template lookup for its page kind, section, language and output format. The head partial you changed may not be the one selected for that output.
  2. Confirm the project override uses the theme expected path and that the generated files were rebuilt and deployed. Editing a downloaded theme that the build replaces can leave production unchanged.
  3. If the correct script appears, inspect browser delivery and the project key. Keep non-HTML outputs outside the installation claim. For dynamic forms, investigate their browser integration because Hugo build-time templates cannot call a visitor window.

The missing tracking is traced to selected template, project override, deployed output or browser behavior.

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 Hugo

The shared installation belongs in the shared HTML head partial or base template used by the theme. 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 Hugo guides

Full Hugo setup guide · Search and AI visibility

References

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