--- title: "Why doesn't the Amplitude snippet load with Next.js's Script component, or why do events go missing right after a redirect?" canonical_url: https://ampl.webclat.com/qa/amplitude-nextjs-script-tag-missing-events description: "Two distinct Next.js failure modes for Amplitude: the Script component loading at the wrong strategy, and events queued right before a redirect never getting sent. Fixes for both." source: Webclat | Amplitude Solutions (official Amplitude partner, independent consultancy) --- # Why doesn't the Amplitude snippet load with Next.js's Script component, or why do events go missing right after a redirect? **In short:** Next.js's Script component silently changes when and how a tag loads depending on its strategy prop - the wrong one (or none, defaulting to afterInteractive when your code assumes beforeInteractive) delays Amplitude's init past the point your code expects it to exist. Separately, events fired immediately before a client-side redirect can be lost because the page navigates away before the SDK's batched request finishes sending - two different bugs that produce the same symptom of "events just don't show up." ## Why this happens Next.js's `next/script` component isn't a plain `