Amir
Forum Replies Created
-
We’re really glad to hear it’s working again, and we truly appreciate you taking the time to let us know!
We also want to sincerely apologize for the inconvenience this issue may have caused over the past few days. We understand how important accurate tracking is, and we appreciate your patience and effort in troubleshooting.
In version 14.13, we made some changes to how the Bypass Ad Blockers feature works. Based on what we’ve seen, it seems that this option may not be functioning correctly on your site. We suspect it could be conflicting with another file or script, which might be causing the issue.
To help us investigate and resolve this thoroughly, it would be very helpful if you could provide us with:
- A list of currently active plugins on your website
- Any relevant JavaScript console errors (from the browser’s developer tools)
- Any PHP errors or logs related to WP Statistics, if available
Before sharing this data, please feel free to remove or mask any sensitive or personal information.
Thanks again for your support and cooperation – we really appreciate your help in improving the plugin!
Best regards,Hi @criticjonni
Thank you for reaching out and for the detailed troubleshooting steps you’ve already taken – we really appreciate it.
From what we can see, it looks like your site might be running behind a CDN in addition to using a caching plugin, and there are also some errors showing in the JavaScript file. To help resolve the issue, please try the following steps:
- Go to Statistics – Settings – General and set the Tracking Method to Client Side Tracking (Recommended).
- Disable the Bypass Ad Blockers option.
- Clear all cached files using your caching plugin (e.g., LiteSpeed Cache).
- If you’re using options like JavaScript file combination/minification in your cache settings, please disable those.
- If your site is also behind a CDN (like Cloudflare), please purge the CDN cache as well to make sure the updated JS files are being served.
Once you’ve completed these steps, please check if the visits start tracking again.
Let us know how it goes – we’re here to assist further if needed!
Regards,Thank you for the update.
We recommend setting the Tracking Method to “Client Side Tracking (Recommended)” for optimal performance.
However, it’s possible that the “Bypass Ad Blockers” option was enabled before the update, and the tracker file may not have been updated correctly during the process. This could potentially cause tracking issues.
To ensure everything is working as expected, please set the Tracking Method to Client Side Tracking (Recommended) and test the tracker in both states – with Bypass Ad Blockers enabled and disabled. Then check whether visits are being recorded correctly in each case.
Your feedback will help us confirm the proper behavior of the Bypass Ad Blockers option.
We truly appreciate your time and cooperation on this!
Best regards,I just wanted to follow up and ask – has the issue been resolved since your last message? Is WP Statistics now tracking visits and other data correctly?
If not, let’s go through a few things that could help identify and fix the issue:
Could you please let us know if you’re using any caching plugins or a CDN on your site? If so, please make sure to clear all layers of cache (including server, plugin, and browser cache).
If you’re using a caching plugin that has JavaScript file combination enabled, try temporarily disabling that option and check if the issue gets resolved. It’s possible there may be a conflict affecting the tracker functionality.
There might be an issue with the tracker on your site. We have a complete troubleshooting guide that can help you debug the tracker performance here:
https://wp-statistics.com/resources/troubleshoot-the-tracker/Also, please go to Statistics – Settings – General, click on Open Debugger, and check if both Tracker.js Status and Hit Endpoint Status show as Successful.
If the problem still persists, please share your site URL with us so we can check the tracker behavior from our end.
We’re here to help you get this issue fully resolved. Just let us know the results of the checks above, and we’ll assist you further.
Best regards,
Hi @slavaws,
Thanks for reaching out!
Could you please let us know if you’re using any caching plugins or a CDN on your site? If so, please make sure to clear all layers of cache (including server, plugin, and browser cache).
If you’re using a caching plugin that has JavaScript file combination enabled, try temporarily disabling that option and check if the issue gets resolved. It’s possible there may be a conflict affecting the tracker functionality.
There might be an issue with the tracker on your site. We have a complete troubleshooting guide that can help you debug the tracker performance here:
https://wp-statistics.com/resources/troubleshoot-the-tracker/Also, please go to Statistics – Settings – General, click on Open Debugger, and check if both Tracker.js Status and Hit Endpoint Status show as Successful.
Could you also please share your site URL with us so we can check the tracker functionality on your end?
We’re here to help you get this resolved as quickly as possible. Looking forward to your response!
Best regards,We’re glad to hear that the issue has been resolved. We apologize for any inconvenience caused during this time and truly appreciate your patience.
If you have any questions or face any issues in the future, please don’t hesitate to reach out to us.
Kind regards,Hi @j1nakayama @u3aredcliffe @jonfabritius
We’re pleased to inform you that the issue mentioned in this thread has been addressed in version 14.10.2, which was just released. Please update the plugin to the newest version, and don’t hesitate to let us know if you experience any further issues.
We truly appreciate your patience and support!
Best regards,Hi @ulim
We wanted to inform you that the issue you reported has been resolved in version 14.10.2, which was released just a few minutes ago. Please update the plugin to the latest version, and let us know if you encounter any further issues.
Thank you for your patience and understanding!
Best regards,Thank you. It is possible that this has caused the difference in the statistics..
We’ve made updates to the Client Side in version 14.10.2, which will be released soon. After the update, please test it again and share your results.
Also, ensure that the Bypass Ad Blockers option is enabled in Client Side.
Regards,Thanks for your message!
Could you please check if Mod Security is enabled on your server?
We look forward to your response.
Regards,Thank you for reviewing and informing us about this matter.
We will investigate this issue and update you with the results soon.
We appreciate your patience.
Could you please send us the list of plugins installed on your site?
You can obtain the complete list by clicking on the “Copy site info to clipboard” option in Tools – Site Health – Info. This will help us identify and resolve the issue more quickly.
Looking forward to hearing from you!
Regards,I hope you’re doing well! I wanted to check in and ask if the issue you were facing has been resolved. Were you able to identify the plugin that was causing the conflict?
If not, please go to Tools – Site Health – Info and click on “Copy site info to clipboard.” Then share that information with us so we can help you better.
Looking forward to hearing from you!
Best regards,Hi @lodree
Thank you for following up and informing us about this matter.
If you are using the latest version of our plugin, please send us the Site Health info of your site by going to Tools – Site Health – Info and clicking on the “Copy site info to clipboard” option.
This will allow us to examine the exact settings applied in the plugin and thoroughly review the items in the Filtering & Exceptions section.
We appreciate your patience and cooperation.
We’ve attempted to replicate the issue using the default configuration but were unable to reproduce the problem. To assist us in diagnosing this further, could you please double-check the configuration you’ve applied?
Additionally, providing any relevant Apache error logs generated during the occurrence of this issue would greatly help us in pinpointing the cause.
Best regards,