@miguelgaton
Thanks for your feedback, I’ll have or Lead Dev @danieliser look into this issue as soon as possible.
Thank you for your patience.
Thanks @waltmesser
Please, keep me informed.
regards,
@miguelgaton – There is no validation to show a popup, it either is targeted to work on a page or not. The pum_analytics stuff is open tracking. The problem is 99% of bots out there don’t process JavaScript, so bots won’t cause that analytics hit to your server as the popup won’t even trigger on a bot request.
This has been tested repeatedly with our more advanced analytics extension which integrates with Google Analytics. We were able to track that its only showing one popup per visitor for instance, yet our site gets hundreds of bot requests a day, so those numbers would have been highly inflated if what your proposing were the case.
In any case PM should have no more performance impact on your site when a bot hits than any other plugin.
Hope that helps.
Hi @danieliser,
Same problem here. On heavy load site pum_analytics stuff has a significant load impact since it’s opening ajax POST to backend servers and impact database performance due to inserts in wp_options table.
I really love your plugin. It’s the best one around! It would be great if there was a button to just disable pum_analytics stuff.
Thanks!
Thank you for the suggestions! We’ll definitely look into implementing this in the future.
Cool! I can’t wait to see this feature! Really appreciated.
Thanks!
@miguelgaton, @merinet – Just to clarify before I add this to our github for resolution, you are aware that you won’t get any information tracked for your popups, no open counts etc? If your using our Popup Analytics extension same thing, no data there either on conversions.
If you don’t need that info I understand but that is by no means a typical use case. That said I would be interested in your servers usage statistics to see how heavy your traffic is to make this an issue. We have sites with a few million hits a day using this with no complaints, though they have cache heavy servers for their front end so 0 requests other than ajax like ours hit the server.
Just interested to know if the issue is one that could be solved on your end allowing you to have best of both.
