DataSag guides · Updated 27 October 2026

Verify DataSag analytics on Next.js Pages Router

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

Start with the Next.js Pages Router installation

Import Script from next/script in pages/_app.tsx. Keep Component and pageProps, and add the tracker once alongside the page component. The shared app stays mounted as users navigate between pages.

Do not install the same tracker in both _app and _document. Do not attach another pageview sender to router.events before testing the tracker's built-in History API handling.

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

  1. Open pages/_app.tsx and confirm that one next/script element sits alongside Component with pageProps preserved. Inspect _document as well so the global installation has a single owner.
  2. Publish a production build and open a page other than the homepage directly. Confirm the shared app loads the tracker and sends a pageview with that page pathname and the intended public key.
  3. Use a Next.js Link to reach another page, then use browser Back. Verify the pageview paths without adding a router.events sender. The _app installation should cover these transitions without remounting a tracker for each page.

The shared Pages Router app records both direct entries and client transitions from one installation.

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

The shared installation belongs in pages/_app.tsx, alongside the page component. Use this as the installation reference while checking the procedure above.

import Script from "next/script";

// Alongside <Component {...pageProps} /> in pages/_app.tsx:
<Script
  id="datasag"
  src="https://www.datasag.com/tracker.js"
  data-datasag-key="YOUR_PUBLIC_KEY"
  strategy="afterInteractive"
/>

Related Next.js Pages Router guides

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

References

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