DataSag guides · Updated 27 October 2026

Verify DataSag analytics on Eleventy

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 Eleventy.

Start with the Eleventy installation

Find the shared layout selected by your Eleventy data cascade, commonly an _includes/base.njk file. Add the deferred tracker to its head while preserving the content placeholder and existing template syntax. Build with your normal configuration and deploy the generated output. Layout paths depend on your project's directory settings.

Eleventy supports multiple template languages and chained layouts. A filename copied from an example may not be the active layout for your content. Inspect layout data and generated pages rather than assuming every collection uses the same wrapper.

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 Eleventy

  1. Trace the layout value for a representative collection item and a standalone page through the Eleventy data cascade. Identify the includes directory configured for this build and the shared layout that emits the document head.
  2. Add or inspect the tracker in that shared head without changing the template's content placeholder. Run the production build and inspect the generated HTML for the actual script source and public-key attribute.
  3. Open the published collection item and standalone page directly, then inspect a custom permalink or layout-free document. Verify its intended coverage separately because collection membership alone does not guarantee the same layout inheritance.

The selected Eleventy layout chain emits one keyed tracker for each intended generated document type.

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 Eleventy

The shared installation belongs in the head of the shared layout resolved from your includes directory. Use this as the installation reference while checking the procedure above.

<script defer src="https://www.datasag.com/tracker.js" data-datasag-key="YOUR_PUBLIC_KEY"></script>

Related Eleventy guides

Full Eleventy setup guide · Search and AI visibility

References

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