DataSag guides · Updated 27 October 2026

Fix DataSag analytics not working on Hexo

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

Start with the Hexo installation

Find the active Hexo theme and its shared layout, such as themes/YOUR_THEME/layout/layout.ejs, or the head partial that layout includes. Add the deferred script once in head, preserving the body placeholder and the theme's template language. Regenerate and deploy the public files before testing.

Hexo templates can choose another layout or disable layout in front matter. Theme updates can overwrite direct edits, so maintain the customization through your theme's supported override or source-control workflow. An unused theme directory cannot affect the current build.

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 Hexo

  1. Check the active theme setting and the affected document's layout front matter. A page can use a different wrapper or disable layout, so a successful article installation does not prove coverage for every generated route.
  2. Inspect the newly generated public files before debugging the browser. Confirm the deployed directory contains this build rather than an earlier output. A saved theme edit cannot change a page that was never regenerated or uploaded.
  3. If a named action is missing, inspect its browser handler in the generated theme assets. Hexo helpers execute at generation time and cannot call a visitor's global tracker. Test the actual form or button after the script executes.

The failure is traced to active-theme selection, regeneration and deployment, or browser action code rather than assumed tracking incompatibility.

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 Hexo

The shared installation belongs in the head of the active theme layout or its shared head partial. 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 Hexo guides

Full Hexo setup guide · Search and AI visibility

References

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