--- title: "Loggle Troubleshooting Guide" url: "https://plugpress.co/docs/loggle-troubleshooting.md" canonical: "https://plugpress.co/docs/loggle-troubleshooting/" published: "2026-08-01" modified: "2026-08-01" author: "Fahim" description: "A step-by-step method for diagnosing any Loggle problem: find whether tracking, storage, or reporting is at fault, then test for plugin conflicts." tags: - "Loggle" --- # Loggle Troubleshooting Guide If you already know your symptom, look it up in [Common Loggle Errors and Fixes](/docs/loggle-common-errors/) — it is faster. Use this page when something is wrong but you are not sure what. It is a method, not a list. ## The idea: three stages, one culprit Loggle does three separate jobs. Almost every problem lives in exactly one of them: 1. **Tracking** — the visitor’s browser telling your site a visit happened. 2. **Storage** — your site writing that visit into the database. 3. **Reporting** — the dashboard reading it back. Find the broken stage first. It saves you from changing settings that were never the problem. ## Step 1: Is it reporting? Test the reading side without involving a browser at all. If you have command-line access: `wp loggle status` This shows whether the three tables exist and how many rows each holds. - **Rows exist but the dashboard is empty or broken** → the problem is **reporting**. Go to Step 4. - **Row counts are zero or not growing** → the problem is earlier. Continue to Step 2. - **Tables are missing** → deactivate and reactivate Loggle to recreate them. No command line? Compare the live widget on your main dashboard with the Loggle dashboard. If the widget sees visitors but reports look wrong, it is a reporting problem. ## Step 2: Is it storage? Record a visit without any browser involved: `wp loggle hit --page=/diagnostic --referrer=https://chatgpt.com/` This runs the real tracking process directly. - **It prints a visit and the row count goes up** → storage is fine. The problem is **tracking**. Go to Step 3. - **It errors, or nothing is stored** → the problem is **storage**: a database permissions issue or missing tables. Check your host’s error log. ## Step 3: Diagnosing tracking The database works, so the visitor’s browser is not reaching it. ### 3a. Are you testing correctly? Use a **private or incognito window**, logged out. Logged-in administrators are not tracked by default, and this is the single most common false alarm. ### 3b. Is the script on the page? 1. Open your site in a private window. 2. View the page source (Ctrl+U or Cmd+U). 3. Search for `tracker.js`. **Not there?** Your theme probably does not call `wp_footer()`. Switch to a default theme like Twenty Twenty-Four and reload. If tracking starts working, your theme is the cause. ### 3c. Is the request being sent? 1. Open your site in a private window. 2. Press F12 to open developer tools and choose the **Network** tab. 3. Reload the page. 4. Filter for `loggle`. You should see a request to `hit`. - **No request at all** → an ad blocker or privacy extension is stopping it, or a JavaScript error earlier on the page stopped the script from running. Check the Console tab. - **A request that fails** → note the status code. A 403 usually means a security plugin or firewall is blocking the address. - **A successful request but no data stored** → the visit is being dropped deliberately. See 3d. ### 3d. Is the visit being dropped on purpose? Loggle ignores some visits by design: logged-in administrators, anything that looks like a bot, and scheduled tasks. If your browser identifies itself unusually, it may be treated as a bot. Test in a normal Chrome or Firefox window before concluding anything. ## Step 4: Diagnosing reporting Data is stored but you cannot see it correctly. ### 4a. Compare against a source that cannot lie `wp loggle summary --range=today` Compare with what the dashboard shows for Today. - **They match** → the data is genuinely what you see. The issue is interpretation rather than a fault — check your date range and any active filters. - **They differ** → a browser-side problem. Hard-refresh with Ctrl+Shift+R, or try a different browser. ### 4b. Check for a stuck filter Clicking a row applies a filter to the whole dashboard. Look for chips near the top of the page and remove any you did not intend. ### 4c. Check the date range Ranges cover whole days ending today. A quiet weekend genuinely looks like a drop. ## Step 5: Test for a plugin conflict If the stages above did not identify it, isolate the cause. 1. Take a backup, and do this on staging if you can. 2. Deactivate every plugin except Loggle. 3. Test the broken behaviour. Still broken? It is not a conflict — go to Step 6. 4. If fixed, reactivate plugins one at a time, testing after each. 5. The plugin that brings the problem back is your conflict. Caching, security, and optimisation plugins are the usual suspects, because they alter requests or defer scripts. ## Step 6: What to gather before asking for help Include these and you will usually get a fix in one reply: - Your Loggle version, WordPress version, and PHP version (**Tools → Site Health → Info**). - Whether your database is MySQL or SQLite. - The output of `wp loggle status`. - Which of the three stages you narrowed it to, and what you saw at that step. - Any errors from the browser console or Network tab. - Whether the problem persists with all other plugins disabled. - Whether you use a CDN, a security plugin, or a caching plugin. ## Things that look like faults but are not - **Your own visits missing** — administrators are excluded by default. - **Numbers lower than Google Analytics** — normal; the tools count differently. - **Locations empty** — expected without Cloudflare. - **Page views older than 90 days gone** — by design. Visitor totals and revenue are kept permanently. - **No comparison on Lifetime** — there is no earlier period to compare against. - **An order with revenue but no channel** — that buyer had no cookie. ## Next steps Once you have identified the stage, the specific fix is likely in [Common Loggle Errors and Fixes](/docs/loggle-common-errors/). To re-confirm a healthy setup afterwards, use [How to Test Whether Loggle Is Working](/docs/test-loggle-tracking/).