Beta · ten sites

Does your site actually work?

Your analytics can tell you how many people arrived, how fast they left and how many pages they touched on the way out. None of that says whether anyone did the thing you built the site for. This starts from that thing and works backwards.

What you are looking at today

  • Sessions
  • Users
  • Pageviews
  • Pages / session
  • Avg. session duration
  • Bounce rate
  • % new sessions

Seven numbers, and not one of them can be acted on. None of them changes what you build tomorrow, because none of them names an outcome.

What you should be looking at

  • How many people did the thing
  • Which channel sent the ones who did
  • Which page they were on when they stopped
  • Which country converts, not just visits
  • What they came for, page by page
  • Whether last month's change moved any of it

Six answers. Each one changes what you do next.

The whole product, on one scroll

No dashboard to build, no report to configure, no metric picker. You get one page, in the order the questions actually get asked.

Example, not a real site

Booked a call

booking_click
37 +18%

out of 512 visits (7.2%), against 31 last period

Channels that convert: search 22/188 (11.7%) · ai 9/41 (22.0%) · direct 6/155 (3.9%)

How they move

Arrived
512
↓ 41% carried on · 302 lost
/pricingmoney
210
↓ 18% carried on · 173 lost
Booked a call
37

Where they come from

ai41 visits · 9 booked (22%)
search188 visits · 22 booked (12%)
direct155 visits · 6 booked (4%)

Invented numbers, real layout: this is the page you get, in this order. The reading takes about four seconds - assistants send a fifth of the traffic search does and convert at twice the rate, and /pricing is where three hundred people stopped.

Two minutes, and you are measured

  1. Put one line in your <head>

    <script defer src="https://analytics.youforgot.marketing/js/a.js" data-site="yourdomain.com"></script>

    No cookie banner, because there are no cookies. Nothing is stored that survives the day.

  2. Say what a win is

    One field. A page they must reach - /thanks/ - or an event your code already fires, like signup_click. The page shows you which events your site is already sending, so you pick from what is real rather than typing from memory.

  3. Read the page

    Is it working → how they move → where they come from → what they came for → what search sees. The funnel builds itself from the paths people actually took; you do not configure one.

Bringing a repository? There is a prompt you paste into a coding agent that writes one file describing your site - what it is, who it is for, what counts as a win - and the console reads it and wires the goals itself. That is the version with no forms at all.

What it will not do

No cross-day journeys

The visitor id is a hash of IP and user agent with a salt that rotates daily, so a person can be counted once within a day and never followed across days. That is a design decision, not a roadmap item - it is what keeps a script on your site out of data-protection territory.

No dashboard builder

You cannot arrange widgets, because the moment a tool asks you which numbers you want, it has handed you the job it was bought to do.

No engagement scores

No invented composite metrics, no "quality score", no benchmark against an industry nobody defined. Every number on the page is something that happened, dated.

No individual profiles

No IP is stored and no person is followed. If you need to know what one named human did on your site, this is the wrong tool and will stay the wrong tool.

Ten sites, and the people behind them

Free during the beta, and your data stays yours. What I want back is one straight answer after a week: did the page tell you something you did not already know, or not. A "no" is worth more to me than a polite yes.

If that question is hard to answer, you are exactly who this is for.