ehamati

Hi @robmaric in this case, we have a few options:

• Disable the “Disable the plugin for known web crawlers” setting by default, or disable it automatically when the Breeze plugin is active.
• Alternatively, manually turn off this setting to avoid such issues.

That said, this behavior is quite unusual. If you’d like us to investigate further, please open a support ticket on the contact page https://www.pixelyoursite.com/contact

• This reply was modified 1 year, 1 month ago by ehamati.

Hello @isabel98, thank you for reaching out via the contact page. I’ve replied to both of your emails. Unfortunately, the first one bounced due to an email issue on your end. However, I responded to the second message you sent today within 5 minutes. Please check your inbox or spam folder, and let’s continue the conversation there so we can work on resolving the issue you’re facing.

Hello @takacszoltan, this issue is related to a setting in the Event Manager called “Track Events Automatically Without Code.” Please make sure to turn this option off, then check again.

Hello @noamel, if you’re experiencing issues with the WooCommerce AddToCart event or button behavior, please follow the steps shown in this video, adjust the mentioned setting, clear your caches, and test again: Click to watch video.

Let me know how it goes,

Enxhi

We have the exact same setup on some of our testing sites without any issues, so it’s hard to pinpoint the problem. It could be related to another plugin, such as a consent solution that isn’t working well with caching. Using multiple caches can sometimes be problematic, especially when updates are released.

For example, if one cache strips the file version, another cache might continue serving the older version without knowing an update exists. This should only happen around updates, but I can’t determine the issue without actually seeing the error.

Additionally, Cloudways (not Cloudflare) support is generally helpful—you might be able to identify the issue with their assistance.

To move forward:

• Try to identify the error in the browser’s console when it occurs and provide us with details.
• Exclude PixelYourSite-related files from Breeze caching:

/wp-content/plugins/pixelyoursite/(.*).js

pixelyoursite-js-extra

I still recommend reaching out to Cloudways support, since it’s their plugin—they may have some useful insights.

Hi @robmaric,

This might be a cache conflict, which can sometimes happen when multiple caching solutions are in use. It’s difficult to pinpoint the exact cause without further debugging. I have a similar setup on some of my test sites without any issues, but Breeze is a particularly aggressive caching plugin and can sometimes cause unexpected behavior—not just with PYS, but in general.

I recommend reaching out to Clouwdays (the developers of Breeze) for further investigation. Additionally, if you’re able to provide access while the issue is occurring, we can attempt to debug it. To proceed with that, please submit a ticket request here:https://www.pixelyoursite.com/contact

You can also check for any errors in the browser’s console at the time of the issue and report them to us for further analysis.

Hello @nikelschubert,

Yes, we use two different names for the dataLayer because the data sent to GTM and GA4 differs. By default, GTM uses “dataLayer”, while GA4 uses “dataLayerPYS”.

We have fixed cases where the dataLayer was written as:
window['dataLayer'] = window['dataLayer'] || [];

It’s important to note that modifying the dataLayer directly in JavaScript isn’t feasible, as some scripts may load before our plugin.

Regarding how we retrieve values for GA consent, we have an example code for using consent filters available on our Filters and Hooks page: https://prnt.sc/arMVzmUmluAo

Best,

Enxhi