Unjournal GA4
51
views · 40 active users · 136 events
2026-10-07–2026-10-10 · Los Angeles reporting time · includes audit traffic
Public aggregate report · refreshed 11 October 2026
The Unjournal: site engagement
Traffic, discovery and useful activity across The Unjournal’s public pages and tools. Snapshot figures retain their original reporting windows; newly installed counters update when this report opens.
Google Search
159
clicks · 5,141 impressions · 3.1% CTR
29 June–28 September; www URL-prefix property only
Requests and distinct IPs are not people. Netlify counts can include crawlers, repeated requests, previews, tests and our own audit. New aggregate counters separately classify recognizable crawlers, respect DNT/GPC, and keep validation traffic separate. They store no IPs, visitor IDs, raw referrers, query strings or submitted text. Browser-like requests can still include bots. Feed polling is not proof of a subscriber. Do not sum metrics with different units, periods or overlapping audiences.
Current traffic
Loading current counts…
Verified Netlify snapshots
| Site | Pageviews | Distinct IPs | Period |
|---|---|---|---|
| uj-prioritization-dashboard | 4,766 | 1,929 | Sep 1–Oct 1 2026 (Oct 1 partial) |
| uj-pba-workshop | 1,194 | 564 | Sep 1–Oct 1 2026 (Oct 1 partial, 13:41 UI) |
| uj-animal-futures-questions | 21 | 11 | Sep 1–Oct 1 2026 (Oct 1 partial) |
| uj-animal-futures-update | 52 | 16 | Sep 1–Oct 1 2026 (Oct 1 partial) |
| uj-pq-workshops | 386 | 220 | Sep 11–Oct 11 2026 (Oct 11 partial, 13:08 UI; UI timezone unverified) |
| uj-wellbeing-workshop | 1,761 | 1,011 | Sep 11–Oct 11 2026 (Oct 11 partial, 13:08 UI; UI timezone unverified) |
| uj-cm-workshop | 5,353 | 1,951 | Sep 11–Oct 11 2026 (Oct 11 partial, 13:06 UI; UI timezone unverified) |
Main-site delivery diagnosis, 2026-10-11. The live homepage is on Squarespace; the Eleventy migration source is not yet serving it. A labelled browser audit was followed by a Realtime pageview and session start, but no user_engagement event. Foreground duration and exact attribution were not verified, so this does not prove a broken tag. Google measures engagement while the page is in focus. A focused visit and received engagement event still need verification; do not infer human use from these tests.
Latest GA4 read-back: 2026-10-07–2026-10-10 (retrieved 2026-10-11). The property reports 51 views, 40 active users and 42 total users. All 136 events are accounted for by 51 pageviews, 43 session starts, 39 first visits and 3 scroll events. No user_engagement, click or completed-use event appears. Average engagement time still displays 0 seconds, so useful engagement is not reliably measured. Reporting timezone is now verified as America/Los_Angeles, separate from the UTC request counters. One labelled audit user/session appears; these figures are not verified human use and recent data may be revised. Investigate engagement delivery and hostname coverage before judging uptake. No account settings changed in this read-back.
What the evidence says
434 of 566 GA4 views (77%) were the homepage. Getting involved had 41 views, the researcher page 15 and evaluator page eight. At least 132 of 159 search clicks (83%) came from the two brand queries. These are separate reporting windows, not a conversion funnel.
GA4 page-view classification repaired on 6 October. The September snapshot reports 99.81% engagement, zero average engagement time and 1,044 key events. Its 566 page views, 477 first visits and one user_engagement event sum to those 1,044 key events. The current account settings confirmed all three were marked as key events; historical setting changes were not reconstructed. Page views are now ordinary events again, removing a trigger that made a landing qualify as engagement. Historical figures retain the old definitions; a fresh complete window still needs checking. First visits and user_engagement remain proxies, with linked primary advertising conversions requiring a campaign-specific audit. No click or completed-action event appears in the September snapshot. Do not interpret its key events as successful use. Google engagement definitions · Key-event changes affect future data.
GA4 delivery check, 2026-10-07. The homepage tag matches the configured stream. An isolated audit received HTTP 204 for a pageview, and Realtime subsequently showed a pageview, first visit and session start. These may be our tests; they do not establish human uptake. The stream also displayed a “no data in 48 hours” warning, so that warning alone is not evidence of a complete outage. Enhanced measurement and automatic event detection are enabled. Accepted engagement delivery remains unverified; an unload request carrying about 20 seconds of engagement was aborted during a test. The Sep 9–Oct 6 report still displayed zero average engagement time, and includes data from before the key-event repair. Inspect a fresh processed window before judging engagement or the repair.
GA4 daily read-back, 2026-10-06 (retrieved 2026-10-07). The report shows 13 active users, 14 pageviews and a displayed 0s average engagement time. All 40 reported events are accounted for by 14 pageviews, 14 session starts and 12 first visits. No user_engagement, scroll, click or completed-use event appears in that window. The homepage bounce rate is 91.7%; this small property-wide window does not establish the cause or success of the repair. Source cards still say mostly complete data, and the property timezone was not verified. The displayed time is rounded. Confirm accepted engagement delivery, then read a fully processed post-change period and hostname split. No account settings changed in this check.
Stored form receipts
Research prioritization · snapshot retrieved 2026-10-11. Cumulative counters at retrieval; historical registration scope not verified.
| Public form | Stored counter |
|---|---|
| Author submissions | 0 |
| Research suggestions | 0 |
| Feedback receipts (combined routes) | 67 |
Stored counters are not unique people or reviewed submissions. Tests, repeated ratings, moderation and registration changes may affect them; no submitted content was fetched. These receipt counters are separate from request/IP snapshots and do not establish a conversion rate. Local monitoring now retains new readings; this public snapshot requires a reviewed refresh. Metadata-only API scope.
Priority improvements
- Verify fresh GA4 engagement figures, consent/GTM delivery and hostname coverage. Record completed interest/newsletter forms after a success response, then audit linked advertising goals before replacing first-visit and engagement proxies.
- Measure research-resource opens and useful prioritization actions. Netlify arrival counts provide a baseline, but do not show evaluation downloads or useful tool outputs.
- Obtain PubPub and GitBook aggregate reports, and improve relevant links from main landing pages and outreach. Counts remain unknown where no report was retrieved.
Public destination inventory
Priority 1 combines relevance, known traffic and active public use. Unknown means unmeasured, not zero. Only approved public destinations are linked; this is not an exhaustive list of every article or historical page.
| Destination | Priority | Observed traffic | Tracking evidence | Next check |
|---|
Snapshots: authenticated platform reports and official analytics summaries. Dates and scope accompany each figure. Historical snapshots require a new export; the request counters refresh automatically. Raw evidence and the wider working inventory remain private.
The Unjournal · Unjournal tools · Netlify metric definitions