DataSag guides · Updated 27 October 2026

Load analytics without blocking rendering on Nuxt

Use the platform's non-blocking external script mechanism and install the tracker once. Measure the published page before and after the change; script size alone cannot predict the effect on your website. 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.

Load analytics without blocking rendering in Nuxt

  1. Keep one deferred external entry in app.head.script and preserve other head configuration. Check whether a plugin already adds async or another loader before measuring a configuration change.
  2. Measure the built production app on a direct route using fixed cache and network conditions. Inspect script execution timing alongside the first useful interaction rather than treating the config flag as a performance result.
  3. Check client-side navigation separately. Head management should not reinstall the tracker on each page. If a useHead call changes the script entry per route, inspect execution and event counts before claiming a loading improvement.

The actual Nuxt browser output uses one non-blocking installation with its timing and event coverage measured together.

Complete the collection checks

  1. Record a baseline of the published page using the same browser, device emulation and network settings you will use for comparison. Include a representative content page, not only the homepage.
  2. Use defer for a normal external HTML script, or the framework-specific loading strategy shown in the installation example. Do not add a parser-blocking synchronous script as a shortcut.
  3. Keep one installation in the shared document or layout. Duplicate execution adds work even if the browser reuses the downloaded file.
  4. Inspect the Network waterfall for tracker.js and /api/track. Compare transfer size, timing and request count on a cold load and a cached load.
  5. Check that measurement still starts at the intended point. Loading only after idle or interaction can omit short visits and early clicks; performance and coverage must be evaluated together.
  6. Repeat the measurements and record variability. Report measured results for your page rather than claiming a universal speed improvement or zero performance cost.
// Browser Console, after loading the published page:
performance.getEntriesByType('resource')
  .filter(entry => entry.name.includes('/tracker.js'))
  .map(entry => ({ url: entry.name, durationMs: entry.duration }));
// Cross-origin transfer details may be unavailable.

What a successful check looks like

The script uses a non-blocking loading mechanism, appears once and records the intended visits. Any performance claim comes from repeatable measurements of the actual site.

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 faster lab result does not prove every visitor has a faster experience. Avoid mixing a warm-cache result with a cold-load baseline.

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.