Closed etc closed 4 months ago
Do you want to try to support both at the same time, or would it be enough to just replace UA with GA4 entirely? A replacement wouldn't be backwards compatible for anyone still using UA, but UA will be gone by July.
Hi @pelargir. I think there are two routes here.
I don't think we need to worry about supporting both UA and GA4. If it were to cause anybody a problem I could help them retro-fit UA config and markup into their site.
But I no longer feel as though GA are the only good option for analytics, and I'd rather Nesta was vendor agnostic, so I have a mild preference for (1).
On the other hand, we don't need to change everything at once, so (2) would be very acceptable to me. I might never get around to writing the docs for (1), though PR's in that department are also welcome — the site is at gma/nestacms.com.
So either approach would be welcome from my perspective. Cheers!
I've created https://github.com/gma/nesta/pull/201 which handles (2) above.
I've just merged #201 ( :clap: ) so closing this.
Will be releasing 0.16.0 shortly…
Google Universal Analytics standard properties will stop processing data on July 1, 2023. So that part of the code can be retired. I don't have the time right now to update Nesta to use the new Google Analytics 4 format instead. But I will do so at some later date if no one beats me to it!