SolutionWright Universal

Transparency

What we measure about you, and only this.

This is the live dashboard we look at ourselves. Same numbers, same queries. There is no second analytics dashboard with names, emails, IPs, or message content — the events table has no column to hold them. Every row below is a derived aggregate (a count, a rate, a bucket). Visitors who send DNT or Sec-GPC arrive unmeasured by construction — no row is written for them, no cookie is set.

The one place we DO keep your name, email, and the words you typed is when you DELIBERATELY submit a form — "begin your free hour," contact, or falsify a claim. Those land in a separate leads table on the same appliance and are visible only to the operator behind a hardware-key login. That table is not shown here; it is not summarized here; it does not color any number on this page. The split is structural — different table, different database role, different code path, different access control.

Read-only. The page renders server-side, has no client JavaScript, no forms, no mutation endpoints, no admin surface.

Signals

First-party, privacy-first analytics on our own iron. Last 24 hours.

88 events / 24h
live read 08:16:31Z
16
Page views
last 24h
100%
Engagement rate
16 engaged (>10s)
40%
Gate solve rate
2 of 5 gate views
0
CTA clicks
0% of views
3
Free-hour intakes
qualified leads
2
Returning visits
came back another day

SEO / GEO self-audit

First-party crawl of 8 key pages + site files. Scored on what crawlers and answer engines actually see. 94/94 checks pass.

100
/ 100

All checks pass — clean SEO + GEO surface.

✓ robots.txt allows + lists sitemap
✓ sitemap.xml reachable + non-empty
✓ llms.txt present (GEO)
✓ llms.txt has citable facts (GEO)
✓ Entity graph: parentOrganization edges
✓ Entity graph: preprint framed unrefereed

Engagement funnel

How visitors move from landing → solving the gate → reaching out.

Page view16
Gate view5
31.3% from previous
Solved / revealed2
40% from previous
CTA click0
0% from previous
Free-hour intake3
0% from previous

Behavioral rates

Engagement (>10s)100%
16 of 16 page views stayed and engaged
Gate solve40%
2 solved vs 0 skipped
CTA clickthrough0%
0 CTA clicks across the site
Sub-5s exits (trust pulse)0%
0 left within 5s with no interaction — lower is better

Traffic sources

How visitors arrived (first-party classification — no third-party trackers).

direct
77 · 87.5%
internal
7 · 8%
unknown
3 · 3.4%
social
1 · 1.1%

AI & search crawler visibility (GEO)

Which answer engines and search bots fetched the site in the last 24h — the first-party signal that the brand graph + llms.txt are being read.

googlebot
11 · 45.8%
other
11 · 45.8%
claudebot
1 · 4.2%
gptbot
1 · 4.2%

Top content (24h)

Most-visited paths.

/transparency
22 · 25.9%
/
22 · 25.9%
/internal/auth
11 · 12.9%
/how-it-works
6 · 7.1%
/api/intake
3 · 3.5%
/packages
3 · 3.5%
/internal/signals
3 · 3.5%
/begin
2 · 2.4%
/mission
2 · 2.4%
/science/the-living-gate
1 · 1.2%
/standard/receipts
1 · 1.2%
/mission/where-the-value-goes
1 · 1.2%
/Download.html
1 · 1.2%
/contact
1 · 1.2%
/work/how-this-was-built
1 · 1.2%
/standard/what-we-do-not-claim
1 · 1.2%
/legal
1 · 1.2%
/science/paper
1 · 1.2%
/PFDownload.html
1 · 1.2%
/RegistrationInfo.php
1 · 1.2%

Privacy posture

Events stored (24h)88
No PII. Coarse cohort id only; salt rotates daily.
Suppressed at mint0 (0%)
DNT / GPC honored end-to-end — nothing stored for opted-out visitors.

The whole schema, in plain English

Every aggregate above derives from exactly these columns in the analytics table. There is no other table.

  • id — an auto-increment row number
  • name — the allowlisted event name (page_view, gate_view, …)
  • path — the page path, canonical (experiment query params stripped)
  • source_bucket — a coarse arrival category (direct, referral, social, …)
  • salted_day_id — an HMAC of (coarse IP + UA family) keyed by the day — opaque, same-day only, cryptographically uncorrelatable across days
  • session_id — a tab-scoped random UUID — dies with the tab
  • variants — JSONB; baked-in experiment variant ids (no content)
  • exp_id — the experiment id, if any
  • deploy_id — the Vercel deploy id (build provenance)
  • props — JSONB; allowlisted derived numerics only (lengths, milestones, scroll percentages)
  • ts — server-assigned timestamp

What is NOT stored, by construction

  • your name
  • your email address
  • your phone number
  • your IP address
  • your User-Agent string
  • the text of anything you typed into a form
  • a durable cross-day visitor id
  • any tracking-cookie value

The two JSONB bags above (variants, props) accept only allowlisted, derived values from the ingest validator on the appliance — they cannot become text-bags for content. Free-text and identifiers are dropped at the boundary, not after.

First-party measurement on the UNI-Lab appliance. No third-party trackers, no cookies for opted-out visitors, DNT/GPC honored end-to-end. Behavioral signal paid SEO/GEO suites can't see — because it never leaves our iron.