Common Loggle Errors and Fixes

Find your symptom below and apply the fix. If your problem is not listed, or you are not sure what the symptom is, work through the troubleshooting guide instead.

The dashboard will not load

“Your session has expired” or “This request was not signed in”

Cause: something between your browser and WordPress is removing the security token Loggle sends, or serving you a cached copy of someone else’s response. Security plugins, aggressive CDNs, and some managed hosts all do this.

Fix:

1. Make sure you are running Loggle 1.0.1 or later, which sends the token a second way specifically to survive this. See How to Update Loggle.
2. Reload the page — an expired token fixes itself on refresh.
3. Exclude /wp-json/loggle/ from your caching plugin or CDN.
4. Temporarily disable security plugins to identify which one strips the header.

“You do not have permission”

Cause: your account cannot manage options. Loggle’s reports are administrator-only.

Fix: log in as an administrator. There is no lower role that can view reports.

The page is blank or stuck loading

Cause: usually a JavaScript conflict with another plugin.

Fix: open your browser console (F12), look for errors mentioning another plugin, and test by deactivating that plugin.

No visits are being recorded

I visit my own site and nothing appears

Cause: logged-in administrators are not tracked by default.

Fix: test in a private or incognito window while logged out. This is correct behaviour, not a fault.

Nothing is recorded even in a private window

Cause: the tracking script is not loading. The most common reason is a theme that never calls WordPress’s footer function, so nothing added to the footer appears.

Fix:

1. Open your site in a private window.
2. View the page source (Ctrl+U or Cmd+U).
3. Search for tracker.js.

If it is missing, your theme is likely missing wp_footer() in its footer template. Ask your theme’s developer, or switch to a default theme to confirm.

Some visitors are recorded and some are not

Cause: normal. Ad blockers, privacy browsers, and blocked cookies prevent tracking for some people.

Fix: none needed. Every analytics tool has this gap. Use your numbers for trends rather than as an exact headcount.

Revenue problems

Revenue shows zero but I have orders

Cause: Loggle records an order when payment completes, not when it is placed.

Fix: check the order status in WooCommerce. Orders sitting in pending, on-hold, or failed have not completed payment yet.

An order has revenue but no channel

Cause: the buyer had no Loggle cookie — they blocked cookies, cleared them between visiting and buying, or bought in a different browser.

Fix: none available. The sale is still counted in your totals; it simply cannot be credited to a source.

Freemius sales are not recorded

Cause: either the credentials are wrong, or the product is not ticked.

Fix: in Settings → Freemius, recheck the Developer ID and both keys for stray spaces, save, then confirm the product is ticked in the list. Only ticked products are recorded.

Report problems

The AI (referred) row shows zero

Cause: usually genuine — you have not had AI traffic in this range yet.

It can also be a limit nothing can fix: some AI tools send visitors with no referrer information, so those arrivals are indistinguishable from direct traffic.

Fix: widen the date range to 30 or 90 days. Loggle keeps the row visible at zero on purpose so you can watch it grow.

Locations are all “(none)”

Cause: country detection relies on Cloudflare sitting in front of your site.

Fix: put your site behind Cloudflare, or accept an empty location report. Loggle deliberately does not download or bundle a geolocation database.

Numbers do not match Google Analytics

Cause: the two tools count differently — sessions, bots, and blocked visitors are all handled differently.

Fix: none needed. Differences of 10–30% between analytics tools are completely normal. There is more on accuracy in the Loggle FAQ.

SQLite sites: visit and payment counts are wrong

Symptom: visitors who clearly returned show only one visit, payment counts sit at zero despite real revenue, and last-click attribution never changes from first-click.

Cause: a fault in versions before 1.1.0 affecting SQLite sites only. Sites on MySQL were never affected.

Fix:

1. Update Loggle to 1.1.0 or later, which fixes the cause.
2. Run wp loggle repair once to correct the figures already stored.

Revenue totals were always correct and are unaffected. Last-click data from before the fix cannot be recovered — it was never written — and the command tells you how many visitors that affects.

Licence errors

“Invalid licence key”

Copy the key straight from your purchase email; stray spaces are the usual culprit.

“No activations left”

Deactivate the licence on a site you no longer use, then activate here.

“Could not reach the licence server”

Your host is blocking outgoing connections. Ask them to allow outgoing HTTPS requests.

Activation errors

“Requires a newer version of WordPress”

Update to WordPress 6.9 or later.

A fatal error on activation

Your PHP version is too old. Loggle needs PHP 8.1 or later — check Tools → Site Health → Info → Server.

Next steps

Still stuck? The troubleshooting guide walks through narrowing a problem down, and tells you what to gather before asking for help. General questions are answered in the Loggle FAQ.