DataSag guides · Updated 27 October 2026

Fix DataSag analytics not working on Nuxt

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

Start with the Nuxt installation

Add one external script entry to app.head.script in nuxt.config.ts. Merge it into existing head settings rather than replacing them. The public project key is intended for the browser; it is not a server credential.

Check whether a plugin or useHead call already installs the same tracker. A server route cannot access window.datasag. Use browser handlers and retain your app's existing consent controls.

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 Nuxt

  1. Check whether the deployed nuxt.config.ts contains the intended script entry and whether a module or environment-specific configuration changes it. Inspect the actual nested-page output before replacing the entire app.head object.
  2. For missing action events, inspect browser guards and execution location. Nuxt server routes and an SSR setup path cannot use the visitor window API. Put the call in the browser handler that receives a successful action result.
  3. Compare direct entry and client navigation on production. If the script exists but the global API is absent, inspect execution and policy errors. If the API exists, inspect the request key and response instead of changing SSR settings.

The diagnosis separates head configuration, SSR execution mistakes, and browser delivery errors.

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 Nuxt

The shared installation belongs in the app head configuration in nuxt.config.ts. Use this as the installation reference while checking the procedure above.

export default defineNuxtConfig({
  app: {
    head: {
      script: [{
        src: "https://www.datasag.com/tracker.js",
        "data-datasag-key": "YOUR_PUBLIC_KEY",
        defer: true
      }]
    }
  }
});

Related Nuxt guides

Full Nuxt setup guide · Search and AI visibility

References

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