What "visitor intelligence" actually means
If you shipped a Lovable MVP in the last six months, your dashboard can tell you how many people arrived. It cannot tell you what any of them wanted. That gap has a name now — visitor intelligence — and the teams shipping the most successful MVPs in 2026 are the ones closing it. Visitor intelligence is not analytics, not session replay, not "did they bounce". It is the layer that answers the question your analytics tools were never designed to answer: what was this visitor trying to do, and how close did your page come to helping them do it?
Why Lovable MVPs feel it first
Lovable gives you a renderer, a database, and Stripe in two clicks. It does not, and is not trying to, give you intent capture. The page renders, the user clicks, the order sometimes lands — and the conversation between arrival and checkout leaves no fingerprint in any database you can query. Google Analytics 4 will tell you the session started. It will not tell you that the visitor typed waterproof under 150 into the filter, paused on the second card, hovered for eight seconds, then left without scrolling further. That signal is sitting on the visitor's screen inside the React component Lovable handed you, and it evaporates the moment the tab closes.
The three signals you are silently losing
The first is typed intent — every phrase the visitor types into the on-page search, the filter, and your chat, which your backend never logs. The second is comparison behavior — the hover-on-card-B-then-card-A-then-back-to-B pattern that says far more about buying intent than any click event ever could. The third is silent exit — the three-minute browse on a single product page that ended in no chat, no add-to-cart, no recorded event of any kind. Your dashboard sees "session ended." Visitor intelligence sees "considered, hesitated, left".
How SiteBridge writes those signals to your table
SiteBridge is one script tag. The widget reads each card's data-product-id, opens a chat sidebar when the visitor lands, and routes whatever they type through /api/parse-intent — an OpenAI endpoint that ranks your catalog against the visitor's stated need. Matching cards highlight; irrelevant ones dim; the page stays still behind the rearrangement. The piece that turns this into visitor intelligence: every typed intent, every hover, and every card rearrangement is logged to analytics_events. So tomorrow morning instead of staring at "sessions: 412, conversions: 3," you open the table and read "17 visitors asked for waterproof boots under $150; 6 of them compared three cards; 2 bought; the other 11 left after comparing two." That sentence is not in your GA4 property today. It is the smallest visitor-intelligence report a Lovable MVP needs to ship.
What makes a visitor intelligence layer different from analytics
Analytics layers report what already happened on the page. Visitor-intelligence layers report what the visitor was trying to do — and ideally, what would have helped them do it. There are three practical signals that distinguish the two: (1) the response is stored in the visitor's own words, not aggregated into a session count; (2) the rewrite happens on-page, in real time, not in a dashboard the visitor will never open; (3) the signal is queryable SQL, not just a pretty funnel chart. If your "intelligence" tool produces only heatmaps and dashboards, it is still analytics wearing a different colored hat.
What to ship today
Three actions before you close the laptop. (1) Paste the SiteBridge snippet from the install guide onto your product page template, just before </head>. (2) Tag every product card with data-product-id — your existing SKU works fine. (3) Check the analytics_events table tomorrow morning and ask yourself which page the 17 "looked but didn't ask" sessions dropped off on, and what they would have bought if the chat had been there. The onboarding hub walks through all three in one guided flow if you'd rather not pick each step apart yourself.
Sources: paraphrased from public Lovable Discord threads, r/ChatGPT posts, and SiteBridge writeups in 2025–2026. Treat the figures as community-reported patterns, not measured data.