Lovable builds your app. anacraft gives you the numbers — who is visiting, what they look at, where they come from. Add GA4 to your Lovable project in one prompt, then ask your AI assistant anything. The data is real, the answers are instant, and you never leave the conversation.
You described an app, Lovable built it, and it is live. Now you need to know if anyone showed up. The GA4 console works, but it is a different tab, a different login, and a different language from where you are already working.
Open anacraft.dev/app, sign in
with Google, pick or create the GA4 property for your app, and copy the
block that goes into Lovable. Nothing to read, four things to click,
nothing on your machine. Rather run it yourself? The same page is
craft serve on your own machine, and every endpoint behind
it is written down.
Sign in with Google. It asks for two Analytics permissions — one to read your numbers, one to create the property for your app — so leave both ticked.
Your Google sign-in is held in that browser tab only: closing it, or an hour, forgets it.
Making one is the usual answer for a Lovable app: give it the app's URL and anacraft creates the property and its web stream, then hands you the measurement ID with the tag already written around it. A site that already has a property is reused, not duplicated.
It is part of
Anacrafter
Elite — $9.99 a month, the same plan step 04 needs — and
the page takes you through subscribing without leaving the flow.
Prefer your own machine? craft serve runs the same
page locally, and craft serve --demo walks it first,
creating nothing.
The copy button gives you instructions, not just a snippet — written for the agent that built the app. Paste it into the Lovable chat, send, and publish.
Those rules are there because an agent will otherwise improve on
a tag it is handed: an npm wrapper instead of the snippet, a
second tag beside the first, or a page view on every route change
that GA4 was already counting. Each one quietly doubles or
hides your numbers. The ID comes in two pieces because Lovable
treats a pasted G- ID as an API key and hides it
from the agent as a secret, and a tag without its ID measures
nothing.
Publish, then craft live to watch the first visit
land.
This is the one step that installs something: craft,
which serves your numbers to the assistant from your own machine.
Sign in, pick your app's property, and write it into Claude
Desktop's config.
Restart the client and ask it how the app is doing. Cursor, Windsurf, VS Code and the raw JSON are on the MCP page.
craft serve --demo walks the whole page on
synthetic data, creating nothing, and
craft mcp --demo does the same for the assistant
— no Google account, no subscription. One
Elite
plan covers both when you are ready for real numbers.
anacraft exposes these tools to your AI client. All are read-only. All carry the date window they cover. All work with the property you configured.
Users, sessions, page views, key events, bounce rate, and session duration — with deltas and a daily trend. The "how are we doing" call.
Who is on the site right now, by country. Realtime, polled every 10 seconds.
Most-visited pages ranked by views.
Events ranked by count, with the previous period for comparison.
Source / medium pairs ranked by sessions.
Users by country, ranked.
Filter pages or events by a substring — "/blog", "purchase", "signup".
Switch between GA4 properties without leaving the conversation.
Each Lovable project gets its own GA4 property. anacraft reads all of them — switch between properties by name or ID without restarting anything.
anacraft is not just an MCP server. Run craft dash
in any terminal for a full-screen, live-updating dashboard with
ore-textured bars, sparklines, and achievement toasts when the
numbers move.
Sign in, give your Lovable app its GA4 property, and ask your assistant anything about your traffic.
