diff --git a/docs/ANALYTICS_INTEGRATION_EXAMPLES.md b/docs/ANALYTICS_INTEGRATION_EXAMPLES.md
new file mode 100644
index 0000000..cd90ada
--- /dev/null
+++ b/docs/ANALYTICS_INTEGRATION_EXAMPLES.md
@@ -0,0 +1,254 @@
+# Vercel Web Analytics Integration Examples
+
+This document provides practical examples of how to integrate Vercel Web Analytics into applications built with the OnChain Test Kit.
+
+## Example 1: React Testing Application with Analytics
+
+For a React application that uses the OnChain Test Kit for E2E testing:
+
+```tsx
+// src/App.tsx
+import { Analytics } from "@vercel/analytics/react";
+import { createOnchainTest } from "@coinbase/onchaintestkit";
+import { CoinbaseWallet } from "@coinbase/onchaintestkit";
+
+export default function App() {
+ return (
+
+
Blockchain Testing Application
+ {/* Your application components */}
+
+
+ );
+}
+```
+
+## Example 2: Next.js Application with Analytics and Wallet Testing
+
+For a Next.js application using the App Router with wallet testing:
+
+```tsx
+// app/layout.tsx
+import { Analytics } from "@vercel/analytics/next";
+
+export default function RootLayout({
+ children,
+}: {
+ children: React.ReactNode;
+}) {
+ return (
+
+
+ Web3 Testing Dashboard
+
+
+
+ {children}
+
+
+
+ );
+}
+```
+
+```tsx
+// app/page.tsx
+import Link from "next/link";
+
+export default function Home() {
+ return (
+
+
Welcome to OnChain Test Kit
+
End-to-end testing for blockchain applications
+ View Test Cases
+
+ );
+}
+```
+
+## Example 3: Testing Dashboard with Analytics
+
+A practical example of a test dashboard that tracks user interactions:
+
+```tsx
+// src/components/TestDashboard.tsx
+import { Analytics } from "@vercel/analytics/react";
+import { createOnchainTest, configure } from "@coinbase/onchaintestkit";
+import { useState } from "react";
+
+export default function TestDashboard() {
+ const [testResults, setTestResults] = useState([]);
+
+ const runTest = async () => {
+ // Track custom event
+ if (window.va) {
+ window.va('event', { name: 'test_run_started' });
+ }
+
+ try {
+ const testConfig = await configure({
+ // Your test configuration
+ });
+
+ const test = await createOnchainTest(testConfig);
+ // Run your tests
+
+ if (window.va) {
+ window.va('event', { name: 'test_run_completed' });
+ }
+ } catch (error) {
+ if (window.va) {
+ window.va('event', { name: 'test_run_failed', error: String(error) });
+ }
+ }
+ };
+
+ return (
+
+
Test Dashboard
+
+
+ {testResults.map((result, idx) => (
+
{result}
+ ))}
+
+
+
+ );
+}
+```
+
+## Example 4: Remix Application with Wallet Support
+
+For a Remix application with real-time wallet testing:
+
+```tsx
+// app/root.tsx
+import {
+ Links,
+ LiveReload,
+ Meta,
+ Outlet,
+ Scripts,
+ ScrollRestoration,
+} from "@remix-run/react";
+import { Analytics } from "@vercel/analytics/remix";
+
+export default function App() {
+ return (
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ );
+}
+```
+
+```tsx
+// app/routes/wallets._index.tsx
+import { MetaMask } from "@coinbase/onchaintestkit";
+import { Link } from "@remix-run/react";
+
+export default function WalletsPage() {
+ return (
+
+
Wallet Testing Tools
+
+
MetaMask Testing
+
Coinbase Wallet Testing
+
Phantom Wallet Testing
+
+
+ );
+}
+```
+
+## Example 5: Sending Custom Events
+
+You can track specific testing events using the `va()` function:
+
+```typescript
+// Track wallet connection
+window.va?.('event', {
+ name: 'wallet_connected',
+ wallet_type: 'metamask',
+});
+
+// Track test completion
+window.va?.('event', {
+ name: 'test_completed',
+ duration_ms: 1234,
+ status: 'passed',
+});
+
+// Track error events
+window.va?.('event', {
+ name: 'test_error',
+ error_type: 'connection_failed',
+ error_message: error.message,
+});
+```
+
+## TypeScript Types for Custom Events
+
+Create a type-safe wrapper for analytics events:
+
+```typescript
+// src/utils/analytics.ts
+export type AnalyticsEvent =
+ | { name: 'wallet_connected'; wallet_type: string }
+ | { name: 'test_started'; test_id: string }
+ | { name: 'test_completed'; duration_ms: number; status: 'passed' | 'failed' }
+ | { name: 'transaction_sent'; chain_id: number }
+ | { name: 'error_occurred'; error_type: string };
+
+export function trackEvent(event: AnalyticsEvent) {
+ if (typeof window !== 'undefined' && window.va) {
+ window.va('event', event);
+ }
+}
+```
+
+## Monitoring Analytics in Development
+
+During development, you can see analytics events in your browser's console:
+
+1. Open your browser's Developer Tools (F12)
+2. Go to the Network tab
+3. Look for requests to `/_vercel/insights/view` or `/_vercel/insights/script.js`
+4. These requests confirm that analytics is working properly
+
+## Troubleshooting
+
+### Analytics not tracking
+
+- Ensure the `Analytics` component is placed at the root level of your application
+- Verify that your app is deployed to Vercel (analytics won't work on localhost)
+- Check the browser's Network tab for requests to `/_vercel/insights/*`
+- Make sure Web Analytics is enabled in the Vercel dashboard
+
+### Missing route information
+
+- Ensure you're using a framework with built-in route support (Next.js, Remix, Nuxt, etc.)
+- For other frameworks, use the `inject()` function instead
+- Note that the `inject()` function does not have automatic route detection
+
+## Best Practices
+
+1. **Minimize tracking overhead**: Only track important events
+2. **Use meaningful event names**: Use clear, descriptive names for custom events
+3. **Avoid sensitive data**: Don't track personal information or secrets
+4. **Test in production**: Analytics only work on deployed Vercel projects
+5. **Monitor performance**: Excessive analytics calls can impact performance
+6. **Document custom events**: Keep a record of all custom events you're tracking
diff --git a/docs/VERCEL_WEB_ANALYTICS.md b/docs/VERCEL_WEB_ANALYTICS.md
new file mode 100644
index 0000000..9cb30a7
--- /dev/null
+++ b/docs/VERCEL_WEB_ANALYTICS.md
@@ -0,0 +1,461 @@
+# Getting started with Vercel Web Analytics
+
+This guide will help you get started with using Vercel Web Analytics on your project, showing you how to enable it, add the package to your project, deploy your app to Vercel, and view your data in the dashboard.
+
+**Select your framework to view instructions on using the Vercel Web Analytics in your project**.
+
+## Prerequisites
+
+- A Vercel account. If you don't have one, you can [sign up for free](https://vercel.com/signup).
+- A Vercel project. If you don't have one, you can [create a new project](https://vercel.com/new).
+- The Vercel CLI installed. If you don't have it, you can install it using the following command:
+
+```bash
+# Using pnpm
+pnpm i vercel
+
+# Using yarn
+yarn i vercel
+
+# Using npm
+npm i vercel
+
+# Using bun
+bun i vercel
+```
+
+## Enable Web Analytics in Vercel
+
+On the [Vercel dashboard](/dashboard), select your Project and then click the **Analytics** tab and click **Enable** from the dialog.
+
+> **💡 Note:** Enabling Web Analytics will add new routes (scoped at `/_vercel/insights/*`) after your next deployment.
+
+## Add `@vercel/analytics` to your project
+
+Using the package manager of your choice, add the `@vercel/analytics` package to your project:
+
+```bash
+# Using pnpm
+pnpm i @vercel/analytics
+
+# Using yarn
+yarn i @vercel/analytics
+
+# Using npm
+npm i @vercel/analytics
+
+# Using bun
+bun i @vercel/analytics
+```
+
+## Add the `Analytics` component to your app
+
+### For Next.js (Pages Directory)
+
+The `Analytics` component is a wrapper around the tracking script, offering more seamless integration with Next.js, including route support.
+
+If you are using the `pages` directory, add the following code to your main app file:
+
+**TypeScript:**
+```tsx
+// pages/_app.tsx
+import type { AppProps } from "next/app";
+import { Analytics } from "@vercel/analytics/next";
+
+function MyApp({ Component, pageProps }: AppProps) {
+ return (
+ <>
+
+
+
+ );
+}
+
+export default MyApp;
+```
+
+**JavaScript:**
+```jsx
+// pages/_app.js
+import { Analytics } from "@vercel/analytics/next";
+
+function MyApp({ Component, pageProps }) {
+ return (
+ <>
+
+
+
+ );
+}
+
+export default MyApp;
+```
+
+### For Next.js (App Directory)
+
+The `Analytics` component is a wrapper around the tracking script, offering more seamless integration with Next.js, including route support.
+
+Add the following code to the root layout:
+
+**TypeScript:**
+```tsx
+// app/layout.tsx
+import { Analytics } from "@vercel/analytics/next";
+
+export default function RootLayout({
+ children,
+}: {
+ children: React.ReactNode;
+}) {
+ return (
+
+
+ Next.js
+
+
+ {children}
+
+
+
+ );
+}
+```
+
+**JavaScript:**
+```jsx
+// app/layout.jsx
+import { Analytics } from "@vercel/analytics/next";
+
+export default function RootLayout({ children }) {
+ return (
+
+
+ Next.js
+
+
+ {children}
+
+
+
+ );
+}
+```
+
+### For Remix
+
+The `Analytics` component is a wrapper around the tracking script, offering a seamless integration with Remix, including route detection.
+
+Add the following code to your root file:
+
+**TypeScript:**
+```tsx
+// app/root.tsx
+import {
+ Links,
+ LiveReload,
+ Meta,
+ Outlet,
+ Scripts,
+ ScrollRestoration,
+} from "@remix-run/react";
+import { Analytics } from "@vercel/analytics/remix";
+
+export default function App() {
+ return (
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ );
+}
+```
+
+**JavaScript:**
+```jsx
+// app/root.jsx
+import {
+ Links,
+ LiveReload,
+ Meta,
+ Outlet,
+ Scripts,
+ ScrollRestoration,
+} from "@remix-run/react";
+import { Analytics } from "@vercel/analytics/remix";
+
+export default function App() {
+ return (
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ );
+}
+```
+
+### For Nuxt
+
+The `Analytics` component is a wrapper around the tracking script, offering more seamless integration with Nuxt, including route support.
+
+Add the following code to your main component.
+
+**TypeScript:**
+```tsx
+// app.vue
+
+
+
+
+
+
+```
+
+**JavaScript:**
+```jsx
+// app.vue
+
+
+
+
+
+
+```
+
+### For SvelteKit
+
+The `injectAnalytics` function is a wrapper around the tracking script, offering more seamless integration with SvelteKit, including route support.
+
+Add the following code to the main layout:
+
+**TypeScript:**
+```ts
+// src/routes/+layout.ts
+import { dev } from "$app/environment";
+import { injectAnalytics } from "@vercel/analytics/sveltekit";
+
+injectAnalytics({ mode: dev ? "development" : "production" });
+```
+
+**JavaScript:**
+```js
+// src/routes/+layout.js
+import { dev } from "$app/environment";
+import { injectAnalytics } from "@vercel/analytics/sveltekit";
+
+injectAnalytics({ mode: dev ? "development" : "production" });
+```
+
+### For Astro
+
+The `Analytics` component is a wrapper around the tracking script, offering more seamless integration with Astro, including route support.
+
+Add the following code to your base layout:
+
+**TypeScript/JSX:**
+```astro
+---
+// src/layouts/Base.astro
+import Analytics from '@vercel/analytics/astro';
+// ... other imports
+---
+
+
+
+
+
+
+
+
+
+
+
+```
+
+> **💡 Note:** The `Analytics` component is available in version `@vercel/analytics@1.4.0` and later. If you are using an earlier version, you must configure the `webAnalytics` property of the Vercel adapter in your `astro.config.mjs` file as shown below.
+
+**For older versions:**
+```ts
+// astro.config.mjs
+import { defineConfig } from "astro/config";
+import vercel from "@astrojs/vercel/serverless";
+
+export default defineConfig({
+ output: "server",
+ adapter: vercel({
+ webAnalytics: {
+ enabled: true, // set to false when using @vercel/analytics@1.4.0
+ },
+ }),
+});
+```
+
+### For Create React App
+
+The `Analytics` component is a wrapper around the tracking script, offering more seamless integration with React.
+
+> **💡 Note:** When using the plain React implementation, there is no route support.
+
+Add the following code to the main app file:
+
+**TypeScript:**
+```tsx
+// App.tsx
+import { Analytics } from "@vercel/analytics/react";
+
+export default function App() {
+ return (
+
+ );
+}
+```
+
+### For Vue
+
+The `Analytics` component is a wrapper around the tracking script, offering more seamless integration with Vue.
+
+> **💡 Note:** Route support is automatically enabled if you're using `vue-router`.
+
+Add the following code to your main component:
+
+**TypeScript:**
+```tsx
+// src/App.vue
+
+
+
+
+
+
+```
+
+**JavaScript:**
+```jsx
+// src/App.vue
+
+
+
+
+
+
+```
+
+### For Plain HTML
+
+For plain HTML sites, you can add the following script to your `.html` files:
+
+```html
+
+
+
+```
+
+> **💡 Note:** When using the HTML implementation, there is no need to install the `@vercel/analytics` package. However, there is no route support.
+
+### For Other Frameworks
+
+Import the `inject` function from the package, which will add the tracking script to your app. **This should only be called once in your app, and must run in the client**.
+
+> **💡 Note:** There is no route support with the `inject` function.
+
+**TypeScript:**
+```ts
+// main.ts
+import { inject } from "@vercel/analytics";
+
+inject();
+```
+
+**JavaScript:**
+```js
+// main.js
+import { inject } from "@vercel/analytics";
+
+inject();
+```
+
+## Deploy your app to Vercel
+
+Deploy your app using the following command:
+
+```bash
+vercel deploy
+```
+
+If you haven't already, we also recommend [connecting your project's Git repository](/docs/git#deploying-a-git-repository), which will enable Vercel to deploy your latest commits to main without terminal commands.
+
+Once your app is deployed, it will start tracking visitors and page views.
+
+> **💡 Note:** If everything is set up properly, you should be able to see a Fetch/XHR request in your browser's Network tab from `/_vercel/insights/view` when you visit any page.
+
+## View your data in the dashboard
+
+Once your app is deployed, and users have visited your site, you can view your data in the dashboard.
+
+To do so, go to your [dashboard](/dashboard), select your project, and click the **Analytics** tab.
+
+After a few days of visitors, you'll be able to start exploring your data by viewing and [filtering](/docs/analytics/filtering) the panels.
+
+Users on Pro and Enterprise plans can also add [custom events](/docs/analytics/custom-events) to their data to track user interactions such as button clicks, form submissions, or purchases.
+
+Learn more about how Vercel supports [privacy and data compliance standards](/docs/analytics/privacy-policy) with Vercel Web Analytics.
+
+## Next steps
+
+Now that you have Vercel Web Analytics set up, you can explore the following topics to learn more:
+
+- [Learn how to use the `@vercel/analytics` package](/docs/analytics/package)
+- [Learn how to set update custom events](/docs/analytics/custom-events)
+- [Learn about filtering data](/docs/analytics/filtering)
+- [Read about privacy and compliance](/docs/analytics/privacy-policy)
+- [Explore pricing](/docs/analytics/limits-and-pricing)
+- [Troubleshooting](/docs/analytics/troubleshooting)