DataSag guides · Updated 27 October 2026

Fix DataSag analytics not working on Ghost

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

Start with the Ghost installation

Add the DataSag script to the site-wide Site Header area of Ghost Code Injection. Replace the example public key, save the change and open the public publication. Keep the active theme's ghost_head helper because that helper outputs header injection. This does not require a DataSag-specific Ghost integration.

Ghost also offers code injection for individual posts. A post-level snippet does not cover the publication, and a theme-level copy can duplicate a global injection. Test a published article and a standalone page outside Ghost Admin.

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 Ghost

  1. Confirm the script is stored in site-wide injection rather than only in one post's settings. Open the affected article without the editor and inspect whether the active theme actually outputs the header injection.
  2. If the tag is absent, check the theme's ghost_head helper and any cache serving the old document. A theme change can remove the helper even though the saved Code Injection field still contains your snippet.
  3. If the script runs but a membership action is missing, distinguish the public theme document from Portal or another hosted flow. Check the tracker request first; do not invent a completed-membership event from a subscribe-button click.

The investigation separates missing publication injection, stale public HTML and actions occurring outside the theme document.

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 Ghost

The shared installation belongs in the site-wide Site Header code injection field. 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 Ghost guides

Full Ghost setup guide · Search and AI visibility

References

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