If your Replo Analytics data suddenly stops tracking (e.g., sessions, conversions, and revenue drop to zero), it's most commonly caused by third-party script blocking or deferring tools installed on your Shopify theme.

Common Cause: Script Blockers

Some performance optimization tools work by intercepting and blocking all third-party scripts from loading until a user interacts with the page (e.g., scrolls, clicks, or moves the mouse). While this can improve initial page load speed, it also prevents the Replo Analytics Pixel from firing — which means analytics data is not captured.

Examples of tools that can cause this include:

• yett.js — a JavaScript library that intercepts document.createElement to block all dynamically-injected scripts until explicitly unblocked

• "Delay JavaScript Execution" features in speed optimization apps

• Custom theme code that defers or blocks Shopify ScriptTags and app extensions

Why This Breaks Replo Analytics

The Replo Analytics Pixel loads via a Shopify ScriptTag (a dynamically-injected <script> element). Script blockers like yett.js intercept the creation of all <script> elements — not just the ones on their blacklist. This means:

• The Replo pixel is blocked on initial page load, even if it's not explicitly blacklisted

• Analytics only starts working after the user interacts with the page (scroll, click, etc.), so initial pageviews and session starts are lost

• If a visitor bounces without interacting, that entire session is never tracked

• Tracking becomes unreliable and intermittent — sometimes events fire, sometimes they don't

How to Confirm This is the Issue

1. Check recent theme changes: Did a developer recently add a speed optimization script or library to your theme.liquid? If analytics was working before and stopped after the change, this is very likely the cause.

2. Check your browser console: Open Developer Tools (F12), go to the Network tab, and look for requests to data.replo.app. If there are none on initial page load, something is blocking the pixel.

3. Use the Replo Chrome Extension: If the extension shows no Replo events firing on your published pages, the pixel is being blocked.

4. Test by removing the blocker: Temporarily remove the script-blocking code from your theme. If analytics data starts appearing again, the blocker was the cause.

How to Fix It

Option A (Recommended): Remove the script blocker and use targeted alternatives

Instead of using a blanket script blocker, use defer or async attributes on the specific scripts you want to delay. This avoids the collateral damage of blocking all scripts — including analytics.

Option B: Whitelist the Replo Analytics Pixel

If you need to keep the script blocker, configure it to allow the Replo analytics script to load immediately. The Replo pixel loads via Shopify app extensions from cdn.shopify.com/extensions/....

Option C: Review blocker behavior

Some script blockers (like yett.js) intercept document.createElement for all scripts, not just those matching a blacklist. Even if Replo isn't on the blacklist, the pixel may still be blocked. Check with the developer who added the blocker to ensure it's not intercepting all script creation.