On this page

Overview

Last updated July 22, 2026

Get vTilt running in minutes — install the script stub, initialize, identify users, track events, and verify in Debug View.

vTilt is a privacy-first analytics platform for any web app. The browser SDK installs at window.vt, batches events to your project, and can forward them to Google Tag, Meta CAPI, PostHog, and GA4.

Follow the Getting Started path in order — each page links to the next via prev/next at the bottom of the article.

#Integration path

Step	Page	What you do
1	Install	Add the SDK via the inline script stub (recommended default) or the npm package — both fully supported
2	Initialize	Call `vt.init('YOUR_PROJECT_TOKEN', { … })` once, as early as possible
3	Identify users	`vt.identify()` on every authenticated page load — not only at login
4	Track events	`vt.capture()` for domain actions; autocapture handles UI clicks
5	Logout & reset	`resetUser()` only on real sign-out
6	Verify events	Confirm `$pageview` in Debug View within ~2 seconds
7	Common mistakes	Pitfalls to avoid before you ship

#Using these docs with an AI agent

Every page is also raw markdown — use the Copy menu on any doc page.

URL	When to use it
`/llms-full.txt`	Paste once; agent ingests the full integration spec
`/llms.txt`	Short index (llmstxt.org); agent fetches pages on demand
`/docs/<slug>.md`	Single page in context

If you connect vTilt MCP, invoke /vtilt:setup first — curated walkthrough (script stub, page-load identify, logout-only resetUser).

#Agent checklist

Prefer the inline script stub from Install — it queues calls before array.js loads and always uses the latest SDK. Use the @v-tilt/browser npm package only if the repo is already bundled with it. Never load both.
vt.init() once, early
identify() on every authenticated page load
resetUser() only when getUserState() === 'identified' and user is null after auth loads
Verify in Debug View

Integrate vTilt into my <stack> app. Read https://YOUR-HOST/llms-full.txt.
Prefer the inline script from /docs/getting-started/install; use the
@v-tilt/browser npm package only if my app already bundles it. Don't load both.
Follow /docs/getting-started/common-mistakes.

text

#What to wire up next

Topic	Page
Your stack (Next.js, Laravel, …)	Integration guides
Event forwarding (GA4, Meta, PostHog)	Event forwarding
Ad-blocker resistant ingest	Reverse proxy
Autocapture, recording, chat	API Reference
Server-side events	Node SDK
AI agent tools (VQL, memory)	MCP server
Website crawl for AI context	Site knowledge

On this page

Overview

Last updated July 22, 2026

Get vTilt running in minutes — install the script stub, initialize, identify users, track events, and verify in Debug View.

vTilt is a privacy-first analytics platform for any web app. The browser SDK installs at window.vt, batches events to your project, and can forward them to Google Tag, Meta CAPI, PostHog, and GA4.

Follow the Getting Started path in order — each page links to the next via prev/next at the bottom of the article.

#Integration path

Step	Page	What you do
1	Install	Add the SDK via the inline script stub (recommended default) or the npm package — both fully supported
2	Initialize	Call `vt.init('YOUR_PROJECT_TOKEN', { … })` once, as early as possible
3	Identify users	`vt.identify()` on every authenticated page load — not only at login
4	Track events	`vt.capture()` for domain actions; autocapture handles UI clicks
5	Logout & reset	`resetUser()` only on real sign-out
6	Verify events	Confirm `$pageview` in Debug View within ~2 seconds
7	Common mistakes	Pitfalls to avoid before you ship

#Using these docs with an AI agent

Every page is also raw markdown — use the Copy menu on any doc page.

URL	When to use it
`/llms-full.txt`	Paste once; agent ingests the full integration spec
`/llms.txt`	Short index (llmstxt.org); agent fetches pages on demand
`/docs/<slug>.md`	Single page in context

If you connect vTilt MCP, invoke /vtilt:setup first — curated walkthrough (script stub, page-load identify, logout-only resetUser).

#Agent checklist

Prefer the inline script stub from Install — it queues calls before array.js loads and always uses the latest SDK. Use the @v-tilt/browser npm package only if the repo is already bundled with it. Never load both.
vt.init() once, early
identify() on every authenticated page load
resetUser() only when getUserState() === 'identified' and user is null after auth loads
Verify in Debug View

Integrate vTilt into my <stack> app. Read https://YOUR-HOST/llms-full.txt.
Prefer the inline script from /docs/getting-started/install; use the
@v-tilt/browser npm package only if my app already bundles it. Don't load both.
Follow /docs/getting-started/common-mistakes.

text

#What to wire up next

Topic	Page
Your stack (Next.js, Laravel, …)	Integration guides
Event forwarding (GA4, Meta, PostHog)	Event forwarding
Ad-blocker resistant ingest	Reverse proxy
Autocapture, recording, chat	API Reference
Server-side events	Node SDK
AI agent tools (VQL, memory)	MCP server
Website crawl for AI context	Site knowledge