DataSag guides · Updated 27 October 2026

Fix DataSag analytics not working on Eleventy

Find the first missing step in the delivery chain: published HTML, executing tracker, tracking request, successful response and project report. Changing several settings at once makes the failure harder to identify. 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.

Fix DataSag analytics not working in Eleventy

  1. Check the affected template's resolved layout data rather than only its filename. Directory data or front matter can override a shared default, and a layout path can resolve differently when the includes directory is customized.
  2. Inspect the output produced by the deployment's actual Eleventy command and configuration. Confirm the server publishes that output directory. Editing a source include does not update old generated HTML until a successful build reaches the host.
  3. For missing custom actions, inspect the generated browser code. JavaScript data files and template helpers execute during generation, so a window.datasag call there cannot record a future visitor action or a later form service response.

The investigation locates layout resolution, deployment-output selection or an incorrectly placed build-time event call.

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