Overview
Understand how project content performs across views, visitors, sessions, active time, scroll depth, sources, devices and interactions.
Problem
A project catalogue becomes more useful when teams can see which content is attracting attention and how deeply people engage with it.
Solution
ProjectBoard records project and public-update engagement and exposes dashboards, session detail and event streams for analysis.
How it works
Review per-project analytics, compare visitor and session patterns, inspect device/source/campaign dimensions, and analyze public update reads and interactions.
Who is this for
Project Manager
Operations
Portfolio Manager
Expected outcomes
- Evidence-based project content decisions
- Visibility into identified and anonymous engagement
- Detailed update-read and interaction reporting
Key metrics
Projects with measurable engagement
0 %
100 %
Time to produce project engagement report
60 minutes
10 minutes
Content decisions backed by engagement data
20 %
80 %
Gallery
Security impact
- Views, sessions, engagement events, device/source dimensions and optional trusted customer context · PII: workspace project data and optional trusted analytics identity context
Compliance
- Analytics access controlled by analytics.view
- Trusted caller context is recorded with analytics where supplied
Availability & next steps
Pro
Business
Enterprise