Not working for GA4 #493
Comments
Also interested in this! |
I am also facing this issue |
I'm also interested in this |
yes please |
I'm also interested in this |
Considering GA4 is now default, this would be a great addition. |
I have rewritten react-ga to support the new Google Analytics 4 in |
I have used this, it is not supported for custom events yet, right? |
@isharadilshan Custom event is supported |
@codler Thanks for your work! I assume that it suppose to be backwards compatible. Is the |
@maxmert I added the alias method |
@codler does this package support both GA4 and UA trackers, or would sending events to multiple trackers need to be all GA4 or UA? |
@ckarras11 Yes, you can either use Multiple trackers are not supported. But it may be possible by instantiate manually |
@ckarras11 Multiple trackers are planned to be supported in autumn |
Awsome, thank you for the timeline! And great work 👍 |
@ckarras11 Multiple trackers are now supported. |
That's amazing, I will look into switching then, thanks for keeping me updated and for working on this 👍 |
Thanks for the great work. |
Thank you so much for working in this! It is truly necessary with the new migration that most of us will have to do to Google Analytics 4 |
Hey @codler do you still maintain the new Google Analytics 4 in react-ga4 https://github.com/PriceRunner/react-ga4? Is it possible to update peer deps for react 18? I tried it with Typescript and getting conflicts |
@BearCooder I don't know what you mean. It doesn't have any dependencies nor peerDependencies. |
@codler sorry you are right I ran into this issue and did not notice it was another package - as I added some simultaneosuly in my package json - that caused the error, my bad sorry! |
Admire all the hard work done for this project. Please update the project to support the new GA4.
Otherwise, users need to toggle the Create a Universal Analytics property toggle button when creating a property in Google Analytics. Then you will get two properties, the old one and the new one. Use the old one (Starting with UA-XXXXXX)
The text was updated successfully, but these errors were encountered: