You launched. The hard question now isn't "did it work" — it's "is anyone actually using it." Answer it by checking five things in order: are real humans arriving (not bots), does anyone complete the one action that defines your product (activation), do they come back (retention), where do they come from, and does anything convert. You can read all five in a day, and most "we have no idea if this is working" launches are really just missing this short list.
Start with real humans, not raw "visits"
The first number most builders see is inflated. Edge and CDN dashboards count HTTP requests, which include crawlers and bots that never run your page's JavaScript — and bots were roughly half of all internet traffic in recent measurement (see how much of your traffic is bots). So before celebrating "2,000 visits," establish how many are people.
In GA4, the closest honest count is Active users: users who had an engaged session, which Google defines as one lasting 10+ seconds, with a key event, or with at least two page/screen views (Google Analytics Help — engaged sessions). A first-party owned event fired on real interaction is even harder for a bot to fake. If active users is a small fraction of "visits," that gap is your bot-and-bounce tax, not your audience.
Did anyone do the one thing that matters
Traffic without action tells you nothing. Every product has one event that means "this person got value" — created a project, sent a message, generated the thing. That's activation, and it's the single most useful number in your first week. Define it as one event, then ask: of the people who arrived, what share did it.
If 500 people landed and 12 activated, you don't have a traffic problem, you have an onboarding problem — and that's a far more actionable diagnosis than a raw pageview chart. Track activation as a key event in GA4 and, ideally, as an owned event so the count survives ad blockers.
Read activation as a rate (activations ÷ active users), and watch where in the path people fall off. If most visitors never reach the screen where activation happens, the fix is your landing and onboarding flow; if they reach it and bail, the fix is that step itself. That single distinction tells you whether to change the top of the funnel or the middle — long before you have enough traffic for any statistical test.
Do they come back
A launch spike is easy; the second visit is the real signal. Retention — the share of new users who return on later days — separates "people checked out the HN link" from "people use this." GA4's retention and cohort reporting shows next-day and 7-day return rates for each cohort of new users.
Don't over-read day one. Look at whether the day-1 and day-7 return lines flatten into a stable band rather than falling to zero. A product nobody returns to has a retention curve that hits the floor fast, no matter how big the launch was.
Where are they coming from
Knowing that people arrived is half the picture; knowing from where tells you what to do next. GA4's Traffic acquisition report breaks sessions down by default channel — direct, organic search, organic social, referral — using source and medium. If a launch post drove a spike, you'll see it; if organic search is quietly growing week over week, that's the durable channel worth investing in.
This is also where owned, paid, and organic should sit side by side. Behavior from GA4, paid performance from Meta, and organic clicks and queries from Google Search Console answer "where do real users come from" far better than any single dashboard — which is the whole point of a normalized cross-source view.
Is anything converting
Finally, the bottom of the funnel: did anyone do the thing that's worth money — subscribe, pay, book. Even at zero revenue, define the conversion event now so the funnel is measurable from day one. Then read it as a rate, not a raw count: signups ÷ active users, paid ÷ trials. Rates stay meaningful as traffic grows; raw counts flatter a launch spike and then look like a collapse.
Put the five on one screen
Active users, activation, retention, source, and conversion are the entire post-launch dashboard you need in week one — and they're more honest together than any one of them alone. The friction is that they live in different places: behavior in GA4, conversions split across GA4 and your own backend, organic in Search Console. Pulling them into one normalized view, with the one weak spot flagged and a suggested next step, is what VibesAnalytics does over MCP or a daily Telegram digest — so "is anyone using it" stops being a feeling and becomes five numbers you check on a Monday. For why the owned-event layer underpins all five, see owned events vs provider events.