integration-tanstack-start

Configure Amplitude client and server tracking for TanStack Start applications.

28|Updated Dec 5, 2025
One-click install
npx skills add https://github.com/amplitude/wizard --skill integration-tanstack-start-amplitude
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-tanstack-start
Source: https://github.com/amplitude/wizard/tree/main/skills/integration/integration-tanstack-start
Command: npx skills add https://github.com/amplitude/wizard --skill integration-tanstack-start-amplitude

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

TanStack Start apps often require coordinated client and server analytics; this skill provides a blueprint to instrument Amplitude across the full-stack workflow.

Core Features & Use Cases

  • Client and server tracking with the Unified SDK on the frontend and the Analytics Node SDK on the backend.
  • Init the Unified SDK with environment keys and enable autocapture for session data.
  • Align event naming and user identification across client and server for easy correlation.

Quick Start

Run the integration wizard to scaffold TanStack Start analytics following the workflow documented in the references.

Frequently Asked Questions about integration-tanstack-start

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up end-to-end Amplitude analytics in a TanStack Start application?

To set up end-to-end Amplitude analytics in a TanStack Start application, initialize the @amplitude/unified SDK on the client and @amplitude/analytics-node on the server, using environment variables for API keys and enabling autocapture for session data.

What is the best way to coordinate client and server tracking in TanStack Start?

Coordinating client and server tracking in TanStack Start requires aligning event naming conventions and user identification across the frontend Unified SDK and the backend Analytics Node SDK for accurate event correlation.

Does the Amplitude Unified SDK work with Node server environments in TanStack Start?

Yes, the Amplitude Unified SDK works with TanStack Start Node server environments by pairing with the @amplitude/analytics-node SDK on the backend to enable full-stack tracking and unified event design.

How do I manage Amplitude API keys across client and server components in TanStack Start?

Managing Amplitude API keys across TanStack Start components requires using environment variables to securely initialize the Unified SDK on the client and the Analytics Node SDK on the server.

Why should I align event naming conventions across client and server Amplitude tracking?

Aligning event naming conventions across client and server Amplitude tracking ensures easy correlation of session data and user actions, preventing fragmented analytics and maintaining a unified event design across the full stack.

Can I use autocapture for session data with Amplitude in a TanStack Start full-stack app?

Yes, you can use autocapture for session data with Amplitude in a TanStack Start full-stack app by initializing the Unified SDK on the client with the appropriate environment keys and enabling the autocapture feature.