vTilt
By roleFoundersKnow what to fix firstMarketersSee what happens after the clickCMOsSee what your budget really buys
By businessSaaSTurn signups into active usersEcommerceSee why shoppers abandon cartsAgenciesProve your work to clientsEnterpriseOne customer record for every team
MeasureWeb AnalyticsFind where buyers leaveSession ReplaySee why they left, not just that they didAdsKnow what paid visitors do nextIntegrationsOne snippet feeds your stack
ThinkPeopleOne profile per customerCustomer MemoryvTilt remembers every visitorSite KnowledgeAnswers and audits from your own pages
ActAsk AIAnswers from real behaviorAI ChatChat that knows the visitorEmail CampaignsEmail from real visits
PricingWhy vTiltDocs
Docs / Studio
Getting Started
OverviewInstallInitializeIdentify usersTrack eventsLogout & resetVerify eventsCommon mistakes
Guides
Event forwardingReverse proxyRealtime dashboardSite knowledgeStudio
Frontend frameworks
Next.jsNuxt.jsVue.jsReactReact RouterRemixGatsbySvelte / SvelteKitAstroAngularTanStack StartDocusaurus
Backend frameworks
NestJSHonoCloudflare WorkersDjangoFlaskLaravelPhoenixRuby on Rails
Backend languages
PythonPHPRubyElixirGoJava.NET / C#Rust
Stack guides
Vue + PHP
API Reference
Browser SDK
Script bundlesAutocaptureWeb VitalsSession recordingChat widgetOutbound messagesFeature readinessRemote configurationDebug logging
Node SDK
Install & setupCapture, identify & aliasContext & shutdownGlobal properties & opt-outError tracking
MCP server
Guides
OverviewAuthenticationOAuthAgent skills (prompts)AI intelligenceSite knowledgeGoogle AdsMeta Ads
Client setup
CursorClaude DesktopVS CodeCodex

Getting Started

OverviewInstallInitializeIdentify usersTrack eventsLogout & resetVerify eventsCommon mistakes

Guides

Event forwardingReverse proxyRealtime dashboardSite knowledgeStudio

API Reference

MCP server

On this page

On this page

  • Open Studio
  • Start an investigation
  • Artifacts
  • Downloading a document
  • Chats history
  • Share a chat
  • Read-only
  • Related
DocsGuidesStudio

Studio

Last updated August 17, 2026

Investigate project analytics with vTilt Studio — an agentic chat workspace over your project data with charts, funnels, and research documents.

Studio is a full-page analytics workspace where you ask questions in natural language and get answers grounded in your project's real data. It runs inside the vTilt dashboard (not as a separate MCP client) and can open charts, interactive explorers, funnels, and multi-page research documents.

#Open Studio

  1. Sign in to your vTilt workspace.
  2. Open a project.
  3. Go to Studio in the project nav (or visit /projects/<projectId>/studio).

Studio uses its own chrome (icon rail + chats panel). Classic dashboard pages remain available from the rail.

#Start an investigation

  1. Click + New chat or type in the empty-state composer.
  2. Ask about traffic, funnels, attribution, event vocabulary, or anything in the project.
  3. The agent narrates briefly, calls read-only analytics tools, and streams an answer. While it works, the thinking indicator shows what it is doing (for example, "Querying your analytics…").
  4. Suggested follow-up chips appear at the end of a turn — tap one to continue.

Example prompts:

  • "Summarize last 7 days of traffic and top pages."
  • "Show me the conversion funnel for the last 30 days."
  • "Where did new users come from this month?"

#Artifacts

When a visual helps, Studio can render:

ArtifactWhat you get
FigureInline chart / infographic (SVG)
TableScrollable data grid
Chart explorerInteractive metric / volume-vs-rate explorer
FunnelStep funnel with drop-offs
DocumentPaginated research report (opens in a viewer; also shows as a PDF/HTML/DOC chip in the chat list)

#Downloading a document

Open a document artifact and use the Download button in the viewer's header to save it as a PDF, a Word document (.docx), or a standalone HTML file. The format matching the chip's badge is listed first, but all three are always available.

Document pages are shown at true A4 proportions, scaled to fit the pane — the zoom readout is a percentage of actual paper size, and clicking it returns to fit-to-width. What you see is what the downloaded file contains.

Note

PDF generation runs server-side. If it is unavailable on your deployment, the viewer says so and the Word and HTML downloads still work.

#Chats history

Sessions are listed in the left Chats panel with title, preview, and artifact chips. Reopening a chat restores the conversation. History is per user and project.

#Share a chat

Open the ⋯ menu on a chat row and choose Share to publish a read-only copy of the conversation. Anyone with the link can read it without signing in or having access to your workspace — they see the messages and artifacts exactly as you do, with no composer and no way to reply.

The link publishes a snapshot taken when you share, not a live feed. Messages you send afterwards stay private until you reopen the dialog and choose Update snapshot, which refreshes the contents while keeping the same link working.

Stop sharing revokes the link immediately — it stops resolving for everyone, including people who already have it. Deleting the chat revokes its link too.

Warning

Anyone holding the link can read the conversation, so treat it as public. Shared pages are excluded from search engines, but the link itself is the only access check — share it the way you would share an unlisted document.

#Read-only

Studio can read project analytics (KPIs, VQL queries, events, docs, site knowledge when enabled). It cannot change project settings, campaigns, or ads from this surface.

#Related

  • MCP server — use the same data tools from Cursor / Claude / Codex
  • Realtime dashboard — live traffic overview without chat
PreviousSite knowledgeGuidesNextNext.jsIntegration guides