GA4-derived views exclude Ashburn. This report now builds from a shared D: content-analytics store, so backend refreshes and backups can move independently of the frontend artifact. The date picker spans the union of imported source dates; GA4, HubSpot email, and LinkedIn each keep their own real coverage windows, shown below. Exact source-to-article attribution is only shown where the GA4 UTM layer supports it.
HubSpot email performance
LinkedIn post performance
GA4 site and article traffic · full year
Ashburn excluded
prepared in Hermes · interactive HTML · built from D: local content store
Pageviews in range
–
…
Email clicks
–
…
LinkedIn clicks
–
…
Top article page
–
…
What mattered most · selected range
Site traffic rhythm · selected range
Where sessions came from · selected range
Quick read
Path to GA4 manual-UTM-tracked article sessions · Ashburn removed
How to read this view
Email drop-off
Email sends by clicks
LinkedIn impression → click conversion
Recent post CTR
LinkedIn posts · impressions vs clicks
Website-driving LinkedIn leaders · selected range
LinkedIn post table
Top article destination pages in GA4 · selected range
Article-side read · selected range
Top destination article pages
Top site pages · selected range
What still needs a better join
The remaining analytical gap is clean article attribution back to each individual email and social post. This report measures feeder performance and destination performance accurately; the next improvement is a stronger URL- or campaign-level join between the two.
Likely bot-heavy direct traffic to monitor
The suspicious geo pattern is concentrated inside Direct, not the controlled feeder channels. Ashburn is excluded across all GA4-derived views in this dashboard. The cards above are a recent monitoring snapshot, not a range-filtered slice.
Email send table · selected range
GA4 UTM reconciliation · Ashburn removed
Estimated read time vs measured engaged time
What this page is showing
Estimated read time is based on article word count at roughly 225 words/minute.
Measured engaged time comes from GA4 user engagement duration divided by sessions for each article.
Word counts are verified article-body counts for the 2026 articles; legacy article counts (marked ≈) are page-text estimates.
Because Ashburn is excluded across the dashboard's GA4-derived layer, these comparisons are cleaner than earlier drafts. They are directional, not a literal completion metric. Article bodies end around 60–71% of full page height on this template, so a blunt 90% scroll proxy would undercount true completion.