DataSag guides · Updated 27 October 2026

Fix duplicate analytics pageviews on Laravel Blade

Multiple tracking requests do not necessarily mean duplicate pageviews. DataSag sends pageviews, scroll milestones, engagement updates and custom events. Inspect eventName before removing code. 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.

Fix duplicate analytics pageviews in Laravel Blade

  1. Search the Blade parent layout, layout components, included head partials and child views for the tracker. A copied snippet in both a layout and a page section produces redundant browser initialization.
  2. Inspect frontend code that handles Livewire navigation, Inertia visits or Alpine initialization if those tools are present. Check for another script insertion or manual pageview mechanism, without assuming every optional Laravel frontend has identical behavior.
  3. Deploy the corrected views and test a direct nested route plus the actual navigation system the site uses. Separate pageview payloads from scroll and goal events. Revisit the route to detect listeners left by repeated frontend initialization.

The tested Laravel frontend retains one installation owner and no overlapping measurement for the same path transition.

Complete the collection checks

  1. Open Network and filter /api/track. Reload once without clicking or scrolling. Inspect eventName in each payload: null identifies a pageview; scroll, click_heatmap and __datasag_engagement are other records.
  2. Count rendered script elements with data-datasag-key. There should be one intended installation for this project. Search your code, site header settings, embeds and tag manager for additional copies.
  3. Remove redundant script insertion mechanisms, keeping the site-wide installation. Two copies execute independently even when their browser download is cached.
  4. Check for custom router listeners that manually send pageviews. The current tracker handles pushState, replaceState and popstate and ignores a repeated pathname. Do not add a second pageview implementation without a demonstrated gap.
  5. Repeat a direct load, a second route and browser Back. Correlate pageview records with actual path changes. A query-only change on the same pathname is not a new pageview in the current tracker.
[...document.querySelectorAll('script[data-datasag-key]')]
  .map(script => ({
    src: script.src,
    key: script.getAttribute('data-datasag-key')
  }));

What a successful check looks like

A single installation and one pageview dispatch for each actual pathname change in the tested sequence. Additional engagement records remain available.

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

Comparing the total number of events with the number of pageviews produces a false duplicate diagnosis. Keep the event categories separate throughout the check.

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.