DataSag guides · Updated 27 October 2026

Fix DataSag analytics not working on PHP templates

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 PHP templates.

Start with the PHP templates installation

Add the deferred external script once to the local PHP include that emits your public HTML head. Preserve the existing document structure and include that file through a known local path in the pages you intend to measure. The tracking snippet itself is HTML; it does not need a PHP analytics library.

An independent PHP endpoint may return JSON, redirect before rendering, or use another header include. Keep the tracker in rendered HTML and avoid inserting output before code that needs to send response headers. Do not derive an include path from visitor input.

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 PHP templates

  1. Inspect the affected public PHP response and its actual include path. A redirect, early exit, JSON response or alternate header file can bypass the snippet even when the source file was uploaded successfully.
  2. Check whether deployment or opcode caching still serves old application output, using the host normal release process. If HTML is absent, do not add output before response-header logic just to force the tracker into a request.
  3. When the real script is present, inspect the public key and browser request response. For a missing action, find the browser handler for the PHP response rather than trying to call a visitor window from server code.

The missing boundary is identified among PHP control flow, deployed include output and browser delivery.

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 PHP templates

The shared installation belongs in the head emitted by the shared PHP header include. 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 PHP templates guides

Full PHP templates setup guide · Search and AI visibility

References

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