Verify DataSag analytics on SvelteKit

Start with the SvelteKit installation

Add the script to head in src/app.html, preserving %sveltekit.head% and the existing body template. That document template loads the tracker once for the application. Replace the public key before building and deploying.

Putting the tracker in a route component can reinstall it on navigation. Keep browser calls out of server load functions and test both direct entry and client-side navigation.

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 SvelteKit

1. Inspect src/app.html and confirm the tracker appears once in head while %sveltekit.head% and the body template remain intact. Do not replace the document placeholders with a copied minimal example.
2. Build and deploy with your chosen adapter, then open a nested route directly. Verify that the delivered document includes the key and that a pageview names the expected pathname.
3. Use a SvelteKit internal link to change routes and use Back. Confirm the tracker observes the path transition without being inserted again by a +page.svelte or +layout.svelte component.

The adapter-served document and SvelteKit client navigation both work from the single app template installation.

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 SvelteKit

The shared installation belongs in the head of src/app.html. 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 SvelteKit guides

• Fix DataSag analytics not working
• Fix duplicate analytics pageviews
• Track custom events
• Track UTM campaigns
• Measure AI referral traffic
• Configure CSP for DataSag analytics
• Exclude your own analytics visits
• Load analytics without blocking rendering

Full SvelteKit setup guide · Search and AI visibility

References

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