Here's what I did to integrate Google Analytics into Astro.
I updated the layout’s
<head> to add the Google Analytics script as early in the
<head> as possible (in my case, after the meta charset tag).
This is a reusable component that takes the Google Analytics measurement ID as a prop.
Partytown isn’t really needed for Google Analytics integration in Astro, but I figured it’s a good idea for a few reasons:
Prevent blocking of page rendering. Third-party scripts will be executed on a separate web worker thread, preventing any scripts from locking up.
Protect from negative impacts of third-party scripts. This includes expensive DOM selectors, CPU-intensive scripts, or blocking network requests, and other negative impacts.
Partytown doesn’t work well with Astro View Transitions.
Doesn’t track page views. (Workarounds are available.) Google Analytics tracking fires a page view event when the page loads. In a SPA (single page app) environment, there needs to be extra tracking code to fire the event manually after a new page is loaded in place.
Breaks in Firefox. No workaround as of Dec 2023. There’s an outstanding bug in Astro 4.0.4 where Partytown breaks View Transitions fallback which is needed for browsers that don’t support view transitions (eg, Firefox).