IMPORT FROM
Google Analytics 4
Connect your Google account and bring historical GA4 data into tinyanalytics. Follow the guide for setup and source-specific limits.
SWITCH TO TINYANALYTICS
Switch without starting over
Add one cookieless tracking script, import the history your team already reports on, then ask your AI agent what changed — TinyAnalytics connects to it over MCP.
HOW THE SWITCH WORKS
Three steps.
Not a migration project.
There is no tag manager rebuild, no data layer to redesign, and no schema to map. Install, import, then point an agent at the result.
- 01
Add one tracking script
One script tag, under 6.5 KB gzipped. Pageviews and single-page-app navigation are tracked automatically, so you can verify the first visit in Realtime before you change anything else.
- 02
Bring your history across
Connect your Google account and TinyAnalytics pulls GA4 history directly — there is no file to download. Plausible, Umami, and Simple Analytics come across as an export file you upload.
- 03
Point your agent at the data
Connect the TinyAnalytics MCP server to Claude Code, Cursor, VS Code, or Codex, then ask for the report you want in plain English instead of rebuilding dashboards by hand.
Imported history is converted into regular events, so it flows through every report — pages, sessions, funnels, retention, cohorts, and period comparison. Import each export once: re-running an import adds the data again rather than replacing it. Read the migration guide
IMPORT YOUR HISTORY
Bring your data.
Keep your context.
Move historical analytics from the tool you use today. Pick your source below for the exact export, connection, and import steps.
IMPORT FROM
Plausible
Export your Plausible history and import the file into tinyanalytics. The guide walks through the required format and steps.
IMPORT FROM
Umami
Move historical Umami data with an export file. Check the guide before importing to understand the supported data.
IMPORT FROM
Simple Analytics
Bring your Simple Analytics export into TinyAnalytics and preserve the historical baseline behind your reporting.
COOKIELESS ANALYTICS
Keep your baseline. Change how you collect.
Your historical data keeps the past useful while one small TinyAnalytics script starts collecting new traffic and product behavior without analytics cookies.
AFTER THE IMPORT
Past context.
Clearer next steps.
Use your imported baseline to understand what changed, then keep new traffic, behavior, conversion, and revenue analysis together.
HISTORY
Compare old and new
Keep the historical trend your team already knows and compare it with the data TinyAnalytics collects next.
REPORTING
Keep analysis in one place
Use one reporting model for acquisition, behavior, conversion, and the historical context behind your decisions.
EXPECTATIONS
Know what carries over
Some source dimensions can be approximate or unavailable. Review the relevant import guide before you switch.
AI-NATIVE
Your analytics,
inside your agent.
TinyAnalytics runs an MCP server that hands 47 tools to the agent you already code with — traffic, site health, events, funnels, revenue, and read-only SQL over your own data. Imported history lands as regular events, so agents query it like everything else.
- Scoped to your key
- The agent reaches only the sites your account can see, and writes respect your organization role.
- No deletion tools
- Sites, goals, funnels, dashboards, and annotations cannot be deleted over MCP.
- Revocable at any time
- Delete the API key in account settings and the agent disconnects immediately.
claude mcp add --transport http TinyAnalytics \
https://dash.tinyanalytics.io/api/mcp \
--header "Authorization: Bearer YOUR_API_KEY"Also works with Cursor, VS Code, Codex CLI.
THEN JUST ASK
- What were my top pages last week?
- How much traffic came from AI assistants this month?
- Which pages do people land on and immediately leave?
- Build me a dashboard of signups per day.