integration-astro-view-transitions

To maintain Amplitude event tracking during Astro view transitions, you need a guarded initialization approach using the Unified SDK's initAll method. This prevents reinitializing analytics during soft navigations, ensuring events remain accurate across ClientRouter route changes.

Amplitude analytics break after ClientRouter soft navigations because the page content swaps without a full reload, often retriggering initialization scripts. Guarding the initialization to run once per app lifecycle prevents duplicate setups and lost event data during these transitions.

You initialize Amplitude in Astro using the Unified SDK by calling initAll with your environment variable API key and enabling autocapture. This setup must be guarded to execute only once per app lifecycle to support ClientRouter view transitions correctly.

Yes, you can track custom events like User Logged In across Astro page transitions. By correctly integrating the Unified SDK with ClientRouter, your custom events fire accurately during soft navigations without being reset or duplicated.

Yes, the Amplitude Unified SDK supports session replay and experiments in Astro. Using the initAll method enables these analytics features alongside event tracking, maintaining their state across ClientRouter view transitions.

Requirements for setting up Amplitude analytics in an Astro app include using environment variables for your API key, enabling autocapture, and ensuring the Unified SDK initializes only once per app lifecycle to support ClientRouter view transitions.