DataSag guides · Updated 27 October 2026

Verify DataSag analytics on Nuxt

A script tag alone does not confirm that analytics works. Verify the published document, the request to DataSag and the matching visit in the correct project. 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.

Verify DataSag analytics in Nuxt

  1. Inspect the merged app.head.script configuration in nuxt.config.ts. Preserve existing head entries and confirm the DataSag object includes its external src, public data attribute, and chosen loading behavior.
  2. Build and publish the Nuxt app, then open a nested route directly. Check the rendered script and tracking request rather than expecting the configuration object itself to prove that the key reached the browser.
  3. Follow a Nuxt internal navigation and use Back. Inspect the pageview path without adding a route watcher. Check plugins and useHead calls if more than one rendered tracker appears.

The shared Nuxt head produces one browser tracker and the tested client navigation reaches the correct project.

Complete the collection checks

  1. Open the published website in a normal browser window with the Network panel recording. Use a browser profile where you can control extensions and your consent choice.
  2. Filter network requests for tracker.js. Confirm it returns JavaScript successfully and that the rendered script has the project's data-datasag-key attribute. The example YOUR_PUBLIC_KEY must be replaced.
  3. Filter for /api/track and reload once. Inspect a request with eventName null or absent. Its projectKey and path should match the chosen project and the page you opened.
  4. Open that DataSag project, choose a date range containing today and inspect the matching path. Use the configured report timezone when checking dates.
  5. Navigate to a second path, then use Back. Compare pageview requests with the route changes rather than counting every request as a pageview.
document.querySelectorAll('script[data-datasag-key]').length
// Expected: 1

document.querySelector('script[data-datasag-key]')?.getAttribute('data-datasag-key')
// Expected: your project's public key

typeof window.datasag?.track
// Expected after the script runs: 'function'

What a successful check looks like

One rendered tracker installation, a successful request for the intended page and a corresponding entry in the intended project. Scroll and engagement requests are separate event types.

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

A successful tracker.js download only proves that a file loaded. It does not validate the project key, consent state or tracking endpoint. Test a real published path before declaring setup complete.

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.