DataSag guides · Updated 27 October 2026
Verify DataSag analytics on Astro
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 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.
Verify DataSag analytics in Astro
- Find the .astro layout used by the affected pages and inspect its head. Preserve the external src and data-datasag-key on the emitted script. Confirm that content collection and standalone pages actually use that layout.
- Publish the Astro output and open a content page directly. Check the real script element and pageview request. A successful homepage test alone does not establish coverage for pages with another layout.
- If the site uses ClientRouter transitions, follow several internal paths and revisit one. Check both pageview paths and the number of script initializations because processed and inline scripts have different transition behavior.
The sampled layouts contain one working installation, with client-transition coverage verified separately where ClientRouter is enabled.
Complete the collection checks
- 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.
- 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.
- 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.
- Open that DataSag project, choose a date range containing today and inspect the matching path. Use the configured report timezone when checking dates.
- 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 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
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.