DataSag guides · Updated 27 October 2026

Fix DataSag analytics not working on Astro

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

Start with the Astro installation

Paste the external script into the head of the .astro layout used by your pages. Keep its src and data attribute on the actual script element. Use is:inline to make the intent explicit and leave the external tracker outside Astro's script bundling.

A layout only covers pages that use it. Check content collection pages and standalone landing pages too. If using client-side transitions, test a full route sequence rather than assuming a fresh document load every time.

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 Astro

  1. Inspect which .astro layout renders the page with missing visits. A collection entry, landing page, or error page can use another layout. Find the script in the actual output instead of assuming every page inherits the homepage head.
  2. Check the emitted script attributes and script-loading response. An external tracker should retain its public key on the real element; investigate bundling or template changes if the published element differs from the reference snippet.
  3. Compare a direct load with a ClientRouter navigation when transitions are enabled. Record where collection stops or repeats. Consult Astro transition lifecycle behavior before adding an unconditional script rerun that could double-initialize tracking.

The failure is localized to layout coverage, emitted script execution, or a specific client-transition sequence.

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 Astro

The shared installation belongs in the head of your shared .astro layout. Use this as the installation reference while checking the procedure above.

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

Related Astro guides

Full Astro setup guide · Search and AI visibility

References

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