Fix DataSag analytics not working on Next.js App Router

Start with the Next.js App Router installation

Import Script from next/script in your root layout. Render the DataSag Script once inside body so it persists across child routes. Keep the existing html, body, providers and children in place. Use strategy="afterInteractive" and replace YOUR_PUBLIC_KEY with the public key copied from your DataSag project.

A Script in a page component or nested layout may disappear or be reintroduced as the route tree changes. Put the single shared installation in the root layout. Browser-only event calls belong in client components, never in a Server Component 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 Next.js App Router

1. Find the root layout that actually wraps the affected route. Route groups or a separate root layout can leave a section outside the installation you inspected. Confirm the deployed layout contains the Script component.
2. Check whether the missing behavior is a pageview or a custom action. A Server Component cannot call window.datasag during rendering. Move an action call into the successful browser handler in a client component.
3. Compare a hard reload with an internal Link transition on production. If the script never runs, inspect loading and policy errors. If it runs but the request fails, inspect its key and response before changing routing code.

The diagnosis distinguishes layout coverage, browser-only action code, and tracking delivery rather than treating every failure as a router problem.

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 Next.js App Router

The shared installation belongs in app/layout.tsx, inside the root body. Use this as the installation reference while checking the procedure above.

import Script from "next/script";

// Inside the existing root layout body, alongside {children}:
<Script
  id="datasag"
  src="https://www.datasag.com/tracker.js"
  data-datasag-key="YOUR_PUBLIC_KEY"
  strategy="afterInteractive"
/>

Related Next.js App Router guides

• Verify DataSag analytics
• Fix duplicate analytics pageviews
• Track custom events
• Track UTM campaigns
• Measure AI referral traffic
• Configure CSP for DataSag analytics
• Exclude your own analytics visits
• Load analytics without blocking rendering

Full Next.js App Router setup guide · Search and AI visibility

References

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