Reporting route
GA4 content and instrumentation dashboard
A site-specific reporting layer for rajeevg.com that keeps the custom schema, portfolio key events, and content performance visible without blending in the hackathon app traffic from the shared GA4 property.
Live reporting boundaries
Historical cards read from property 498363924 and filter to rajeevg.com. Realtime custom-event cards lock to stream 11542983613 so the main site’s vocabulary stays visible even though the shared property also collects vote.rajeevg.com.
Historical cards are filtered to hostName=rajeevg.com so the shared property does not blend in vote.rajeevg.com page traffic.
Realtime custom-event cards are filtered to the main-site stream ID so the app-owned site schema stays front and center.
No tracked custom events are visible in realtime right now. The dashboard still keeps the schema and historical page reporting visible while traffic is quiet.
The chart toggle redraws the same live dataset two different ways so it is easier to compare narrative summaries, categorical breakdowns, and realtime event spikes without leaving this route.
Page views
5
All main-site page views in the historical window, filtered away from the hackathon app.
Active users
1
Distinct active users seen on rajeevg.com across the last 30 days.
Avg engagement
5.6m
Average engaged time per active user, using GA4’s engagement-duration metric.
Blog share
20%
Share of tracked views coming from blog pages in the current reporting window.
Top blog pages
The most-read blog URLs on the main site, combining headline volume with the audience behind it.
Device mix
A quick read on whether the audience is leaning desktop, mobile, or tablet in the current host-filtered window.
Realtime custom events
The site-owned vocabulary visible in the last 30 minutes, filtered to the main-site GA4 stream.
No tracked custom events are visible in realtime right now.
Portfolio key events
The conversion-like interactions that matter most on the public site, separated from raw event volume.
Top blog pages
The content pages currently carrying the most reading volume on the main site.
/blog/when-not-to-use-server-side-tagging
When Not To Use Server-Side Tagging • Rajeev G.
Views
1
Users
1
Engagement
4.3m
Realtime custom events
The main-site custom event vocabulary currently visible in GA4 Realtime.
No tracked custom events are visible in realtime right now. That usually means the main site is quiet, not that the schema disappeared.
Portfolio key events
Key-event rows promoted for the site’s conversion-like interactions.
project_click
6 total event hits in the retained window
6
profile_click
2 total event hits in the retained window
2
Device mix
How the current site traffic splits across device classes.
desktop
1 usersViews
5
Engagement
5.6m
Full-site page leaders
The highest-volume pages on the main site across blog, projects, and supporting routes.
Home
Rajeev G.
Views
1
Engagement
0m
/analytics
Analytics hub • Rajeev G.
Views
1
Engagement
56s
/blog/when-not-to-use-server-side-tagging
When Not To Use Server-Side Tagging • Rajeev G.
Views
1
Engagement
4.3m
/projects/site-analytics
Projects • Rajeev G.
Views
1
Engagement
25s
/proof
Proof • Rajeev G.
Views
1
Engagement
0m
Promoted site dimensions
Event-scoped fields promoted on the GA4 property so the site-owned schema is usable in reports and explorations.
Promoted site metrics
Numeric event parameters preserved as first-class reporting metrics.
Why this route exists
The shared property is now good enough that it deserves a site-owned reading surface, not just a GA admin tab.
Front and center
The dashboard keeps the blog pages, project pages, current custom event stream, and promoted schema in one place so the site’s content analytics do not get flattened into default page_view tables.
Related reading
Same live GA4 payload, two renderer systems, one route to review.