Load analytics without blocking rendering 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.

Load analytics without blocking rendering in Next.js App Router

1. Use next/script in app/layout.tsx with afterInteractive for the documented installation. Check the shared layout before adding another loader. A normal script in a child component can add execution work without improving coverage.
2. Measure a direct production entry with the same throttling and cache settings before and after the change. Inspect when tracker.js runs relative to the Next.js application and whether an early intended action occurs before tracking is available.
3. Navigate with internal Links after the first load. The root installation should persist without a new loader on each route. If evaluating lazyOnload, explicitly test short visits and early clicks because later loading changes measurement coverage.

The chosen Next.js loading strategy is measured on direct entry and client navigation, with the effect on early events recorded.

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 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 DataSag analytics not working
• Fix duplicate analytics pageviews
• Track custom events
• Track UTM campaigns
• Measure AI referral traffic
• Configure CSP for DataSag analytics
• Exclude your own analytics visits

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.