alekv
Forum Replies Created
-
Thanks for your nice review 🙂
Hi.
I’m the developer of the Pixel Manager for WooCommerce. And yes, I can confirm that if you enable the Google Consent Mode in the Pixel Manager, it will disable the Google Consent Mode in Cookiebot. You should not enable it in both places. Our recommendation is to only enable it in the Pixel Manager, which will ensure that all tracking works fine for Google.
Hi jh
Thank you so much for your fantastic review! It is super motivating, and we will keep giving our best for you and all our users.
Kind regards
AleksandarThis will take longer to dig into, especially now with Easter coming up.
I’ll look into this a bit closer, and we’ll come back in a few days.
Hi @dany897
In our previous direct message to you, we already explained that we couldn’t replicate what you experience.
Could you please send us a step-by-step guide, ideally with screenshots that show what you see and that helps us to replicate how you identify the issue. Once we can replicate it on our site, we will be able to address it properly.
Thanks
Aleksandar@boybawang the only thing that the Pixel Manager does in the background is it schedules a nightly update on the payment gateway diagnosis.
I have seen problems before in combination with the action scheduler. I didn’t have access to the remote server, but I assume it was a third-party script or plugin that deleted action scheduler tasks and therefore re-triggered that background task. But this only would have happened while browsing the Pixel Manager settings. So the conditions are very narrow for this bug to appear, and it is unlikely that that’s what you have run into.
Other than that, the Pixel Manager has no code in it that would cause anything that would explain what you experience. It just doesn’t run any background tasks. And you ruled out those two features that could put load on the server, (which is also clearly documented in our documentation).
Your description doesn’t really show any causality the Pixel Manager and the server load spikes.
Since you don’t want to share any types of logs, I’d suggest you deactivate the Pixel Manager.
I just would appreciate it if you want to blame the Pixel Manager to come up with some proof that would help me fix it.
@boybawang then it is very unlikely that the Pixel Manager is causing any of this.
If you can provide any logs, I’ll be happy to provide additional support to identify what’s causing the load on the server. If the logs contain information that you don’t want to share publicly, you can send them over to support@sweetcode.com
@boybawang Thanks for the feedback. Maybe you can help us here.
I wonder how to properly address this. Two features in the Pixel Manager can put load on a server. The Google Tag Gateway, when not proxied through Cloudflare, and server-to-server event tracking (Meta CAPI, etc.).
We documented both clearly in the Pixel Manager, that when those features are activated it can increase the load on the server and might require to upgrade the server or to disable the features.
I’m torn between several sides.
– The Pixel Manager users like those features and Google, Meta, etc. are recommending to use them. So our users tend to keep those features activated, which puts load onto the servers (depending on the server stack configuration from 0% to a lot).
– Hosting providers just see the additional load, don’t care too much about certain settings in the plugin and then recommend turning off the entire plugin.
What could I do to satisfy both sides better?
I thought about removing the GTG feature if it can’t be proxied through Cloudflare. But, I don’t like that idea. We are in an open eco system and I like our users to have a broader choice.
Any idea how to tackle this?
You could have just disabled the Google Tag Gateway and server side tracking.
It is documented in our documentation that those features can cause more stress on the server and if enabled must be managed (tweaked, disabled or the server upgraded).
You still have those options.
A fix for this has been released with version
1.55.1Haha. Thanks for that comment 🙂
It’s a bug and will be fixed with the next release in the next 24 hours.
A fix for this has been published. Feedback is welcome.
Thanks for this fantastic review!
I’m glad the Pixel Manager if of such value for you.Hi @rermis
Thanks for reporting this.
This message certainly shouldn’t appear in all those places that you have sent screenshots for.
We do have other scoped notifications that only show up on the WordPress dashboard, but not everywhere else. This notification seems not to follow that scope, so this needs to be fixed. We’ll do that with one of the next coming releases.Side note: In practice it is allowed to use the admin dashboard for notifications. Even WordPress does it for their paid plugins.