Please go to ‘GTM Kit > Help > Support > Share system data with the GTM Kit support team’ and enter the support ticket: FS869-870E9
Thread Starter
Egl
(@egletiere)
Hi!
Do you have any answer on the issue?
We also noticed this error message in dev console even though the pixel variable is correct and pixel seems to be getting data: Uncaught ReferenceError: fbq is not defined
It seems like you are not using the standard GTM Kit container implementation. Have you manually inserted the container script or are you using some kind of optimization plugun?
Thread Starter
Egl
(@egletiere)
Google Tag Manager script is manually added to before wp_head(); and noscript is manually added at the beginning of body. Both show up correctly in source. Datalayer also shows up correct in source.
We previously had some issues with noscript not showing up so we decided to manually add both.
-
This reply was modified 1 year, 1 month ago by
Egl.
-
This reply was modified 1 year, 1 month ago by Egl.
Are you receivin data in Google Analytics? The warnings in Google Tag Manager are often wrong, of if you are receiving data in Google Analutics i would not worry
Thread Starter
Egl
(@egletiere)
Google Analytics receives data and all events fire.
Pixel also receives data and all events fire – before using your template it was set up differently so we see a large drop in events but I presume that’s normal.
I understand your point about GTM being wrong but I want to make sure everything is set up correctly and also want to resolve the console issue I mentioned before (ata: Uncaught ReferenceError: fbq is not defined)
The error “Uncaught ReferenceError: fbq is not defined” occurs when a Custom HTML tag or similar script attempts to execute fbq(‘track’, ‘something’); before the Facebook Pixel (fbq()) is initialized.
Are you using the GTM templates from GTM Kit?
Thread Starter
Egl
(@egletiere)
Yes, we use GTM templates from GTM Kit, constant – Facebook Pixel ID is set correctly and for now we paused these tags: Google Ads – Conversion Tracking, Google Ads – Remarketing and Google Ads – Conversion Linker – this last one might not have been included in your template and been added by me. I don’t quite remember.
Thread Starter
Egl
(@egletiere)
I forgot to mention that the console error appears only on product pages
Check in Tag Assistant if the FB pixel fires before any other FB tags
Thread Starter
Egl
(@egletiere)
The first one to fire after Consent is Google Tag – GA4 Configuration (Initialization) and Pixel fires afterwards (Container_Loaded).
Should I set Pixel tag to also fire at Initialization or leave it All Pages?
You just need to make sure that the FB pixel fires before any other FB events. Du you have another plugin that or any other service/script that may be firing af FB event before the pixel is fired?
Thread Starter
Egl
(@egletiere)
I’ve switched the Pixel to be fired at Initialization – All Pages instead of All Pages. Now it is visibly firing before other FB events but the error still appears in console.
I suspected that this plugin was firing the events but it was not after all… (Product Feed PRO for WooCommerce). I really don’t know how to test where that error comes from.
Regarding Google Tag Manager should I investigate further or should I disregard the Urgent warnings?
-
This reply was modified 1 year, 1 month ago by Egl.
-
This reply was modified 1 year, 1 month ago by Egl.
In my experience the new GMT notifications/warnings are buggy and most can be disregarded, which i woud do in your case
