Runtime fingerprintToken readout from the active provider chain.
Live DS
Runtime
PlatformRottay
Rottay / ModernPlatform Flagship
Primary
#FFFFFFSecondary #A0A0A5
Radius
Compact runtime evidence across 3+ token signals.
Published DS package ยท Tenant Showcase ยท Rottay / modernShared route metadata for the active runtime, kept inline so the shell reads like a thin header band.
Palette
#FFFFFFRottay
Chrome
Modernrenderer posture
Radius
14pxsurface shape
Density
normalPlatform Flagship
Back to Evnto
Analytics4 scenario rowsTier mix 0P / 1S / 19Pr
Scenario summary
Analytics in Evnto balances premium presentation with live-event clarity.
Analytics in Evnto pulls together attendance, commercial performance, and engagement so teams can understand what really happened before the next event. These scenarios stay Evnto-specific in workflow and copy, but the live visuals should still come from the active docs runtime instead of a local preset.
Scenario rows4Named modules that anchor this category's product story.
Unique parts12Distinct structures, patterns, and primitives in this category.
Dominant archetypeAnalytics surfaceThe prevailing interaction shape across these modules.
Scenario rows
Scenario modules
Each row below captures a product-grade module, the component spread behind it, and what to scrutinize when the runtime changes.
Read orderStart with the title and archetype, then inspect composition balance and the part sample.
Proof checkConfirm the lane still reads like one product module after the runtime changes tone, density, and contrast.
01
Scenario module
Attendance Dashboard
Check-in rate tracking with peak-hour heatmaps and no-show analysis.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 1S / 4Pr
Inspect forCheck whether chart emphasis, contrast, and labels stay legible under the active provider.
Supporting partsRepresentative pieces behind this scenario lane.
StatsHeader
LineChart
HeatMap
Card
+1 more
02
Scenario module
Revenue Analytics
Revenue trends with forecasting, seasonal patterns, and growth metrics.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 0S / 5Pr
Inspect forCheck whether chart emphasis, contrast, and labels stay legible under the active provider.
Supporting partsRepresentative pieces behind this scenario lane.
LineChart
BarChart
Statistic
Card
+1 more
03
Scenario module
Engagement Metrics
Attendee engagement scores, session popularity, and interaction heatmaps.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 0S / 5Pr
Inspect forCheck whether chart emphasis, contrast, and labels stay legible under the active provider.
Supporting partsRepresentative pieces behind this scenario lane.
RadarChart
BarChart
Card
Progress
+1 more
04
Scenario module
Marketing ROI
Channel attribution, conversion funnels, and campaign performance comparison.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 0S / 5Pr
Inspect forCheck whether chart emphasis, contrast, and labels stay legible under the active provider.
Supporting partsRepresentative pieces behind this scenario lane.
Event-product flows showing how the system flexes for experience-heavy UIs.
Runtime controls
TenantRottay
EngineModern
Operators
LeadershipRevenue teamsEvent analysts
The category has to stay legible for these roles even when a different tenant runtime shifts density or contrast.
Tempo and pressureReview, optimization, and forecastingUse the scenario rows below to verify that hierarchy and control placement still hold up at this pace.
Design principles3 guardrails
Principle 01Blend operational and commercial insight.
Principle 02Keep trend reading simple and obvious.
Principle 03Support post-event action, not passive reporting.
Active provider
Runtime audit
Rottay is rendering this appendix.
Use this page as a reference sheet: the scenario modules stay constant, while contrast, shell tone, and component personality respond to the active docs runtime.
Runtime
PlatformRottay
Rottay / ModernPlatform Flagship
Primary
#FFFFFFSecondary #A0A0A5
Radius
Compact runtime evidence across 3+ token signals.
14pxxl 18px
Density
normalBorder-light cards
Accent
Badge
roundedtop bar ยท solid dividers
Motion
springHover lift 2px
Keep stableAnalytics still needs to feel native for Leadership, Revenue teams, and 1 more even while the provider changes the surrounding chrome.
Stress pointReview, optimization, and forecasting means hierarchy, action placement, and contrast cannot become ambiguous under a different runtime.
Read as one laneAnalytics surface should feel like one coherent chapter here rather than a stack of isolated component demos.