DataSag guides · Updated 27 October 2026

Fix DataSag analytics not working on Shopify storefront themes

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 Shopify storefront themes.

Start with the Shopify storefront themes installation

Back up or duplicate the theme first. Add the tracker to layout/theme.liquid before </head>, using the public key for the storefront project. Save the theme and test the published storefront. This is a theme integration, not a Shopify app installation.

The theme does not control every checkout or customer account document. A storefront pageview does not prove a completed order. Do not claim this snippet measures checkout pages or purchase revenue without a separate supported integration.

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 Shopify storefront themes

  1. Confirm which Shopify theme is live, then inspect its layout/theme.liquid. Editing a duplicate theme does not update the storefront until you publish it. Preserve a backup before changing the live theme.
  2. Compare a storefront product page with the page where tracking is absent. Checkout and customer-account surfaces can use documents the theme does not control, so a working theme snippet cannot establish their coverage.
  3. On an affected storefront page, inspect the actual script, public key, browser errors, and endpoint response. Check any existing consent gating without bypassing it. Do not install another theme copy to solve a separate checkout integration problem.

The diagnosis distinguishes unpublished theme changes, storefront delivery, and pages outside the theme boundary.

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 Shopify storefront themes

The shared installation belongs in layout/theme.liquid before the closing head tag. 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 Shopify storefront themes guides

Full Shopify storefront themes setup guide · Search and AI visibility

References

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