# Tracwell

> Privacy-aware product analytics for websites and React Native applications.

## Documentation

- [Get started with Tracwell](https://tracwell.app/docs.md): Create a project, install an SDK, and verify the first analytics event.
- [Connect Tracwell to your agent](https://tracwell.app/docs/agents.md): Connect Codex, Claude Code, Cursor, or VS Code to Tracwell's MCP server for analytics and scoped goal/funnel writes.
- [Browser SDK](https://tracwell.app/docs/browser-sdk.md): Install Tracwell's browser SDK and configure automatic page-view tracking.
- [React Native SDK](https://tracwell.app/docs/react-native.md): Install Tracwell for React Native and track screens, events, and identity.
- [Framework integrations](https://tracwell.app/docs/frameworks.md): Initialize Tracwell once in a framework's browser lifecycle.
- [Custom events](https://tracwell.app/docs/events.md): Configure, name, track, and verify custom analytics events.
- [Server events](https://tracwell.app/docs/server-events.md): Record backend-confirmed actions with visitor identity and safe delivery retries.
- [Identity and sessions](https://tracwell.app/docs/identity.md): Understand Tracwell collection modes, visitor identity, and sessions.
- [Consent and privacy](https://tracwell.app/docs/privacy.md): Configure consent and privacy controls in Tracwell.
- [Revenue attribution](https://tracwell.app/docs/revenue.md): Connect live payment-provider access and attribute verified revenue to its originating session.
- [Reports and metrics](https://tracwell.app/docs/analytics.md): Understand Tracwell overview, acquisition, events, journeys, funnels, goals, and revenue.
- [Troubleshooting](https://tracwell.app/docs/troubleshooting.md): Troubleshoot Tracwell collection, validation, identity, routing, and delivery.
- [React](https://tracwell.app/docs/frameworks/react.md): Mount one client-only component near the root. The module-level client prevents React Strict Mode from initializing Tracwell twice in development.
- [Next.js](https://tracwell.app/docs/frameworks/nextjs.md): Keep initialization in a small Client Component and render it from the root layout. The rest of the layout can remain a Server Component.
- [React Router](https://tracwell.app/docs/frameworks/react-router.md): Initialize from the root route or application shell. Effects run only in the browser, including framework-mode applications that render on the server.
- [Remix](https://tracwell.app/docs/frameworks/remix.md): Initialize from app/root.tsx. The effect is skipped during server rendering and stays mounted across nested routes.
- [Vue](https://tracwell.app/docs/frameworks/vue.md): Create the analytics client in the browser entry before mounting the application. Provide it when components need direct event tracking.
- [Nuxt](https://tracwell.app/docs/frameworks/nuxt.md): Use a client-only Nuxt plugin. The .client suffix keeps browser initialization out of server rendering.
- [Svelte](https://tracwell.app/docs/frameworks/svelte.md): Initialize Tracwell in the browser entry before mounting the Svelte application.
- [SvelteKit](https://tracwell.app/docs/frameworks/sveltekit.md): Initialize from the root layout with onMount. The callback runs in the browser and is skipped during server rendering.
- [Astro](https://tracwell.app/docs/frameworks/astro.md): For Astro, the CDN script is the simplest integration. Put it once in the shared layout.
- [Angular](https://tracwell.app/docs/frameworks/angular.md): Use a root-provided service and guard initialization with isPlatformBrowser when the application uses server rendering.
- [Solid and SolidStart](https://tracwell.app/docs/frameworks/solid.md): Initialize from a root component with onMount. Solid runs onMount once in the browser and skips it during server rendering.
- [Qwik](https://tracwell.app/docs/frameworks/qwik.md): Analytics needs eager browser initialization in Qwik, so use a root-level visible task with the document-ready strategy.

## Service endpoints

- Collector script: https://collect.tracwell.app/script.js
- Event collector: https://collect.tracwell.app/v1/events
- Server custom events: https://collect.tracwell.app/v1/server/events
- Server revenue: https://collect.tracwell.app/v1/server/revenue
- MCP server: https://tracwell.app/mcp

## Usage for agents

1. Fetch this index to choose the relevant guide.
2. Fetch the linked Markdown guide instead of parsing the HTML documentation.
3. Follow the framework-specific initialization boundary.
4. Never place server keys or MCP keys in client-side code.
5. Use the custom events guide for validation and privacy limits.