DataSag guides · Updated 27 October 2026

Fix DataSag analytics not working on Gatsby

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

Start with the Gatsby installation

Use the Gatsby SSR onRenderBody API to add one deferred external script through setHeadComponents. Merge the addition into an existing hook rather than overwriting it, and keep the React import required by your file format. Build and publish the generated site; inspect its HTML because this hook concerns generated documents.

A browser onRouteUpdate hook, a plugin and gatsby-ssr can all add analytics behavior. Do not add a second pageview sender without testing the current tracker. gatsby develop is not a substitute for checking generated production documents.

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 Gatsby

  1. Confirm the deployed Gatsby build includes the gatsby-ssr hook change. A hook added only to gatsby-browser does not prove the generated HTML contains the tracker for direct entries.
  2. Inspect the actual generated page source and browser errors. If the script is missing, check hook composition and build output before changing component state or installing another plugin.
  3. For missing custom actions, inspect the browser success handler rather than build-time Node execution. Compare a direct page load with Gatsby Link navigation and record whether another plugin changes loading or route behavior.

The diagnosis separates generated HTML ownership, deployment output and browser action or navigation behavior.

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 Gatsby

The shared installation belongs in an onRenderBody head component in the root gatsby-ssr.js file. Use this as the installation reference while checking the procedure above.

const React = require("react");

// Merge into your existing onRenderBody hook if one exists.
exports.onRenderBody = ({ setHeadComponents }) => {
  setHeadComponents([
    <script key="datasag" defer
      src="https://www.datasag.com/tracker.js"
      data-datasag-key="YOUR_PUBLIC_KEY" />
  ]);
};

Related Gatsby guides

Full Gatsby setup guide · Search and AI visibility

References

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