DataSag guides · Updated 27 October 2026

Verify DataSag analytics on Laravel Blade

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

Start with the Laravel Blade installation

Add the deferred external script once in the shared Blade layout under resources/views, inside its existing head. Preserve @vite, component slots and content sections. Determine whether your pages use template inheritance or a layout component before choosing the file. Deploy the view change through your normal application release.

An alternate authentication layout or a standalone Blade view may not use the same head. Livewire navigation and Inertia change the browser lifecycle; verify their route sequences separately instead of promising coverage from a normal Blade page test.

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 Laravel Blade

  1. Trace the web route to its Blade view and parent layout or layout component. Confirm the tracker appears in the shared head outside a child section that removes it. Preserve the existing asset and component directives.
  2. Deploy the view change and open a public nested route directly. Inspect the rendered script and public key. If your deployment caches compiled views, use its normal release process to ensure the new view is active.
  3. Open a route using an alternate layout, such as your public authentication page. Check its actual pageview request. If Livewire navigation or Inertia is present, record a separate client-navigation test rather than inferring coverage from a full load.

The deployed Blade inheritance paths contain the intended script, with any alternate client-navigation system tested explicitly.

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 Laravel Blade

The shared installation belongs in the head of the shared Blade layout used by your web routes. 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 Laravel Blade guides

Full Laravel Blade setup guide · Search and AI visibility

References

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