When applying the gatsby-plugin-google-gtag plug-in, it must be applied at the top of the plug-in plug-in list to work well. I kept thinking about it because the data stream wasn't analyzed, but the plug-in order was important
Followed this to the T and still no analytics. Am getting a 307 status for the gtag. I think the plugin might be pushing out javascript that is preventing the gtag to be communicated? "if(true) { window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'G-4XJYSFRSR9', {"send_page_view":false}); }". I don't know if something broke in the plugin?
Hi, that was very useful. It was superb. I loved your lucid explanation. It will be nice if you can make another video about how to handle custom events like click etc. using this plugin.
At @Guiding Digital thank you, thank you, thank you. This was great. As a non-developer, I can easily pass this along to my dev team to help them through the needed changes. Question: are there any problems with keeping the gatsby-plugin-google-analytics plugin (for our old universal analytics properties) and then using g-tag for our new unified GA4 properties? We have a bunch of custom configuration set-up using the gatsby-plugin-google-analytics plugin that I'd prefer to not touch (our plan is to depreciate our universal analytics properties after we have 13 months of data in our new GA4 property), but not sure if it's possible to use the gatsby-plugin-google-gtag and the gatsby-plugin-google-analytics plugin at the same time?
Thank you very much, you really helped me out. I couldn't find this information anywhere.
This is a gold mine. I needed this. Thanks for sharing!
Glad it was helpful!
When applying the gatsby-plugin-google-gtag plug-in, it must be applied at the top of the plug-in plug-in list to work well.
I kept thinking about it because the data stream wasn't analyzed, but the plug-in order was important
Followed this to the T and still no analytics. Am getting a 307 status for the gtag. I think the plugin might be pushing out javascript that is preventing the gtag to be communicated? "if(true) {
window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'G-4XJYSFRSR9', {"send_page_view":false}); }". I don't know if something broke in the plugin?
Do you know what is the reason/benefit of using gatsby-route-chage event instead of native page_view?
Hi, that was very useful. It was superb. I loved your lucid explanation. It will be nice if you can make another video about how to handle custom events like click etc. using this plugin.
Thanks. I'll add that to my list of potential future videos.
@@GuidingDigital Thanks a lot for considering that.
how to set up converttion for google ads
Same here
At @Guiding Digital thank you, thank you, thank you. This was great. As a non-developer, I can easily pass this along to my dev team to help them through the needed changes.
Question: are there any problems with keeping the gatsby-plugin-google-analytics plugin (for our old universal analytics properties) and then using g-tag for our new unified GA4 properties?
We have a bunch of custom configuration set-up using the gatsby-plugin-google-analytics plugin that I'd prefer to not touch (our plan is to depreciate our universal analytics properties after we have 13 months of data in our new GA4 property), but not sure if it's possible to use the gatsby-plugin-google-gtag and the gatsby-plugin-google-analytics plugin at the same time?
UA and new GA4 implementations should operate in tandem without issue I think!