odeezl

I looked around for if disabling the pixel can be pushed from GTM but did not find a way to do that.
I ended up just disabling it from the function.php file and added all the Facebook pixels manually via GTM.
Thanks for the support!

@tipat here is what I’m working on right now and why I think keeping the events would be good.

Since we like to use GTM to manage scripts I needed to find a solution to implement GDPR compliance on the website since all of the plugins available for WP does not provide a logical way to work with GTM.

What I found is working with OneTrust can get the job done, I followed this guide which explains in detail how to make it work.

By following the guide, in GTM you will have control over which pixels are fired and which not depending on the cookie setting selected by the user which is ideal and what we are looking for.

This only leaves the “issue” with Facebook for Woocommerce which adds the pixel “plugin side” and not “GTM side” and can not be controlled with this method.
Which brings me to my request. If we can only disable the “page view” pixel form firing from the “plugin side” we can set that in GTM and control based on user cookie settings. Since the “page view” pixel contains the Facebook library js, if it’s not firing, events will not be registered anyway so no need to disable these.

To conclude, if the events are kept in “Facebook for woocommerce” we can only fire the “page view” pixel from GTM when we need it, and all events will work from “Facebook for woocommerce” side. If the “page view” is nor firing, these events will not be registered anyway.
This way we keep some of the benefits of “Facebook for woocommerce” and save time creating all these events in GTM.
I hope this makes sense 🙂

• This reply was modified 5 years, 11 months ago by odeezl.