DataSag guides · Updated 27 October 2026

Fix DataSag analytics not working on VitePress

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

Start with the VitePress installation

Merge a script tuple into the global VitePress head array. Include the external src, an empty-string defer attribute and the public data-datasag-key. Preserve other head entries, build the documentation and inspect its published HTML. Global config covers ordinary pages generated from that site.

VitePress also supports page-level head entries in frontmatter and custom theme code. A global script plus page or theme insertion can execute twice. Browser APIs belong in browser interaction code, not the Node-evaluated site configuration or an SSR render.

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 VitePress

  1. Confirm the configuration is under the VitePress root used by the deployed command. A monorepo can contain several .vitepress directories. Inspect the actual generated HTML to establish which head configuration reached the affected page.
  2. Check whether a page-level head entry or theme customization differs from the global setup. Preserve the source and public-key attributes together; a script URL that loads successfully still cannot identify the project without its key.
  3. If the missing item is a custom action, inspect its Vue browser handler rather than the site config. A server-rendered setup path cannot safely access window.datasag. Reproduce the action after the external tracker has loaded.

The investigation distinguishes the selected documentation root, missing script attributes and browser-only Vue action handling.

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 VitePress

The shared installation belongs in the head array in .vitepress/config.ts or its configured equivalent. Use this as the installation reference while checking the procedure above.

// Merge into the existing .vitepress config.
export default {
  head: [["script", {
    src: "https://www.datasag.com/tracker.js",
    defer: "",
    "data-datasag-key": "YOUR_PUBLIC_KEY"
  }]]
};

Related VitePress guides

Full VitePress setup guide · Search and AI visibility

References

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