DataSag guides · Updated 27 October 2026

Fix DataSag analytics not working on WordPress

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 WordPress.

Start with the WordPress installation

Use a maintained site-wide header injection mechanism, or add a wp_head callback in your own child theme or site plugin. Paste the script into the header field once. Avoid editing a parent theme file that an update can overwrite. Publish and clear the relevant page cache.

Theme header settings, a header plugin and a tag manager can all inject scripts independently. Search each installation location. WordPress.com and managed plans can restrict custom scripts; confirm your plan permits JavaScript before changing themes or plugins.

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 WordPress

  1. Confirm the selected WordPress hosting plan permits custom JavaScript. Then inspect the active injection location, theme, and plugin state. A snippet stored in an inactive theme cannot affect the current public pages.
  2. Compare a logged-out public response with the editor or administrator view. Clear the page cache that still contains the old document, and check whether an optimization or consent plugin delays or removes the tracker.
  3. If the script executes but visits remain absent, inspect the project key and endpoint response. Keep a record of the affected template and plugin behavior before disabling unrelated extensions or editing parent-theme files.

The failing layer is identified among plan restrictions, active injection, cached output, plugin processing, and request 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 WordPress

The shared installation belongs in a site-wide head injection or the wp_head hook. 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 WordPress guides

Full WordPress setup guide · Search and AI visibility

References

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