Common issues¶

This page helps you troubleshoot the most common BimBeau Privacy Analytics issues from a user perspective.

Use it when reports look empty, tracking seems incomplete, Pro features are not visible, exports do not download, Events do not trigger, or the PWA Stats App behaves unexpectedly. For settings-specific help, review Settings overview and Tracking and privacy.

Quick troubleshooting checklist¶

Start with these checks before investigating a specific issue.

1. Confirm BimBeau Privacy Analytics is active

   Open Plugins in WordPress and confirm that BimBeau Privacy Analytics is active.

2. Open BimBeau Privacy Analytics from WordPress admin

   Go to BimBeau Privacy Analytics → Dashboard and check whether the interface loads.

3. Check the selected date range

   Many reports depend on the selected period. Make sure you are viewing a range that includes recent traffic.

4. Visit a public page

   Open a normal public frontend page of your website, then return to BimBeau Privacy Analytics and refresh the report.

5. Review tracking and privacy settings

   Check role exclusions, advanced tracking settings, consent behavior, and retention settings.

Dashboard is empty¶

An empty dashboard usually means BimBeau Privacy Analytics has not collected enough activity for the selected period.

Try this:

1. Check the date range

   Select today or a recent period.

2. Generate a test visit

   Open a public frontend page in a browser.

3. Refresh the dashboard

   Return to BimBeau Privacy Analytics → Dashboard and refresh the page after a short moment.

4. Check role exclusions

   If your WordPress role is excluded from tracking, your own test visit may not be recorded.

5. Compare with Real-time

   Open BimBeau Privacy Analytics → Real-time to check whether recent activity appears there.

Real-time shows no activity¶

Real-time only shows recent activity. If your site has no recent visitors, it can be empty even when BimBeau Privacy Analytics is working correctly.

Check the following:

• open a public frontend page as a visitor;
• avoid testing only from WordPress admin screens;
• check whether your user role is excluded from tracking;
• check whether a cache, security, or consent tool is blocking expected scripts;
• compare with the Dashboard or Pages report.

Cache or optimization plugin blocks tracking¶

BimBeau Privacy Analytics uses front-end JavaScript trackers to record page views and consent-based enriched activity. The essential tracker should not be delayed until user interaction, because visitors who leave before interacting may not produce a page-view hit.

Most minification, defer, and optimization setups work with the tracker scripts. Aggressive JavaScript delay, combine, or reorder features may still require exclusions for the tracker runtime.

Recommended exclusion patterns:

bbpa-essential-tracker
bbpa-advanced-tracker
bbpa-essential-tracker.js
bbpa-advanced-tracker.js
__bbpaRuntimeConfig
data-bbpa-runtime-config
/wp-content/plugins/bimbeau-privacy-analytics/
/wp-content/plugins/bimbeau-privacy-analytics-pro/

If a security or firewall plugin blocks analytics requests, allow POST requests to this REST endpoint:

/wp-json/bbpa/v1/hits

LiteSpeed Cache troubleshooting¶

For LiteSpeed Cache, purge all caches after changing optimization settings. If tracking stops, temporarily disable JavaScript Combine, Minify, Defer, and Delay options, test that /wp-json/bbpa/v1/hits accepts requests, then re-enable optimization settings progressively with the exclusions above.

My own visits are not recorded¶

Your own visits may be excluded by design.

Possible reasons:

Referring sites are missing or shown as direct¶

Referrer data can be incomplete. This is normal in many situations.

A visit may appear as direct traffic when:

• the visitor typed the URL;
• the visitor used a bookmark;
• the source app did not share referrer information;
• the browser restricted referrer data;
• the referring website used a strict referrer policy;
• privacy tools removed the referrer.

Internal searches are empty¶

Internal searches appear only when BimBeau Privacy Analytics can record internal website search activity.

Check that:

• your website has a search form or supported internal search experience;
• visitors have used the search feature during the selected period;
• the selected date range includes those searches;
• tracking is enabled and not blocked by exclusions;
• your own test search is performed on the public frontend.

404 errors are not appearing¶

The Pages not found view shows missing public URLs requested on your website.

To test it:

1. Open a fake public URL

   Visit a clearly invalid URL on your website, such as /this-page-does-not-exist-test.

2. Confirm WordPress returns a not found page

   Make sure the page really displays a 404 or not found state.

3. Refresh BimBeau Privacy Analytics

   Open BimBeau Privacy Analytics → Pages, then open Pages not found and check the selected date range.

If the URL redirects instead of returning a 404, it may not appear as a 404 error.

Geolocation is incomplete¶

Geolocation depends on available technical signals and configured geolocation sources.

Some visits may not resolve to a country or city. City-level data is often less complete than country-level data.

Check the following:

• geolocation settings are configured as expected;
• the selected date range includes traffic;
• consent behavior allows expected enrichment where required;
• your geolocation database or provider setup is current;
• the report has enough traffic to show meaningful patterns.

Some visitor fields are private or unavailable¶

This is often expected.

Visitor fields can be limited when:

• only essential tracking data is available;
• advanced tracking is disabled;
• analytics consent was not granted;
• the browser did not provide a usable signal;
• geolocation data was unavailable;
• timing data was not collected.

Average active time looks low or missing¶

Average active time depends on active engagement signals.

It may be low, zero, or unavailable when:

• visitors leave quickly;
• visitors keep the page open without active engagement;
• advanced tracking is disabled or blocked;
• timing data is not available for the selected period;
• the selected page has too little traffic;
• consent rules prevent enriched tracking.

Average active time is not the same as full session duration.

Pro features are not visible¶

If Pro features are missing, check the following:

1. Confirm Pro is active

   Make sure your Pro license or account connection is active.

2. Check your WordPress user permissions

   Your user account must have access to BimBeau Privacy Analytics and Pro features.

3. Refresh WordPress admin

   Reload the BimBeau Privacy Analytics admin screens after activating or connecting Pro.

4. Check plugin version

   Make sure you are running the expected BimBeau Privacy Analytics version.

5. Review the feature location

   Some Pro features appear inside settings, specific reports, or table actions rather than as separate menu items.

Export button is missing¶

Exports are a Pro feature and may appear only on supported reports.

Check that:

• Pro is active;
• your user has permission to export;
• the current report supports exports;
• the selected table or view contains data;
• you are not expecting exports on a report that does not support them yet.

Export does not download¶

If an export action is visible but no file downloads, try this:

1. Check browser downloads

   Make sure your browser did not block the download or save it to another folder.

2. Reduce the date range

   Large exports can take longer or be harder to generate. Try a shorter period.

3. Try another format

   If multiple formats are available, try CSV or JSON.

4. Check permissions again

   Your session or permissions may have changed.

5. Retry from a supported report

   Try exporting from a common supported report such as Pages or Referring sites.

Events do not trigger¶

Events are a Pro feature and may depend on advanced tracking.

Check the following:

• Pro is active;
• the event is enabled;
• the trigger type is correct;
• the CSS selector, form selector, or page pattern is correct;
• the event is tested on a public frontend page;
• your role is not excluded from tracking;
• analytics consent allows advanced tracking where required;
• cache or script optimization is not blocking BimBeau Privacy Analytics scripts.

Event appears twice¶

An event may appear more than once if multiple triggers match the same visitor action.

Common causes:

• tracking both a click and a form submission for the same form;
• using a selector that matches multiple elements;
• configuring overlapping page view patterns;
• repeated clicks by the same visitor;
• custom scripts triggering the same behavior more than once.

Review your event configuration and simplify overlapping triggers when needed.

PWA Stats App does not open¶

If the PWA Stats App does not open, check:

• Pro is active;
• your user has permission to access BimBeau Privacy Analytics;
• you are signed in with the correct WordPress account;
• security plugins are not blocking app routes;
• cache or optimization plugins are not blocking app assets;
• the normal BimBeau Privacy Analytics admin screens still work.

PWA Stats App looks outdated¶

Because the PWA Stats App can use app-like browser caching, the interface may occasionally appear outdated after an update.

Try this:

1. Refresh the app

   Reload the browser tab or app window.

2. Close and reopen it

   Fully close the app or browser window, then open it again.

3. Compare with WordPress admin

   Open BimBeau Privacy Analytics in the standard WordPress admin to check whether the issue is app-specific.

4. Clear site data if needed

   If the app still appears outdated, clear site data for your website in the browser.

CMP or consent issues¶

If advanced tracking, Events, active time, or enriched visitor details do not behave as expected, review your CMP setup.

Check that:

• the advanced tracker is assigned to the correct analytics or statistics category;
• the advanced tracker is blocked before consent if your policy requires it;
• the advanced tracker is allowed after consent;
• cache or script optimization does not change the script in a way that breaks CMP matching;
• you test both declined and accepted consent states;
• you test as a logged-out visitor.

Cache or script optimization issues¶

Performance plugins can sometimes delay, combine, move, or block scripts.

If tracking or Events stop working after optimization changes:

1. Temporarily disable optimization

   Turn off script delay, combination, or minification to see whether the issue disappears.

2. Exclude BimBeau Privacy Analytics scripts

   Exclude BimBeau Privacy Analytics tracking scripts from aggressive optimization rules.

3. Test as a normal visitor

   Use a private browser window and a public frontend page.

4. Re-enable optimization gradually

   Turn optimization features back on one by one to identify the conflicting rule.

Historical data disappeared¶

Historical reports can become empty if data retention cleanup removed old data.

Check:

• the selected date range;
• aggregate data retention settings;
• whether cleanup has run;
• whether the data exists in an export or backup;
• whether uninstall cleanup was enabled before removing the plugin.

Still stuck?¶

When asking for help, collect the following information:

• your WordPress version;
• your PHP version;
• your BimBeau Privacy Analytics version;
• whether you use Free or Pro;
• the report or feature affected;
• the selected date range;
• whether the issue happens for logged-out visitors;
• whether a CMP, cache plugin, security plugin, or script optimizer is active;
• screenshots of the relevant BimBeau Privacy Analytics screen if possible.