Hi @peterborg, thanks for getting in touch and for sharing this. I’d be happy to investigate this further for you. Please could you first share the information below:
- Your Site Health information. You can use this form to share privately if preferred.
- Does this have any impact on the functionality of Site Kit when you are using it?
- Does the same occur when following the troubleshooting steps here?
Once you have shared the above information I can review and suggest some next steps should there be any to take. Let me know if you have any other questions at this time.
Hi Ad,
I’ve submitted a request in the Site Kit by Google | Site Health Information form.
Should I close this?
@peterborg Thanks for sharing the information that’s very helpful. I can see the error myself when checking on your website. Could you please confirm that if you deactivate the Site Kit plugin, does this console error go away?
I’ve just disable the plugin and as you can see the error is not login in the console
@peterborg Yes, I can see the console error is no longer there. Thanks for doing that. I will carry out some further tests and discuss this further with the team and once I have an update I will share it here.
@peterborg While I haven’t been able to replicate the issue you are facing, I believe the issue is a conflict between Site Kit and another plugin you have active on your site which may be modifying the add to cart button functionality and thus preventing Site Kit from accessing necessary data for plugin conversions.
With this in mind, I’d suggest checking this by activating Site Kit and one by one temporarily disabling other active plugins and checking the add to cart button each time. If you get to a stage where this stops, then the last plugin disabled would be the one conflicting with Site Kit.
We are also looking to see if there is anything we can do on our side to help prevent this happening but if you could test as suggested above and find a conflict, that would help us to replicate the issue ourselves and find a better solution if possible.
Thanks for your patience with this while we investigate. Let me know if you have any other questions.
As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist.
I think i found the conflicting plugin, you can close this for now, if need be ill re-open it
@peterborg Thanks for the update, that’s great to hear. If you could share the information on what the conflicting plugin was that would be great. we can then perform some checks ourselves to ensure that there isn’t anything we can do on our side to help with this, thanks!
