Time controls let you define what time period to analyze and at what granularity to view the data. Every report in Trodo supports flexible time configuration.
✅ Good combinations:├── Last 24 hours → Hourly granularity├── Last 7 days → Daily granularity├── Last 30 days → Daily or weekly├── Last 90 days → Weekly granularity├── Last 365 days → Monthly granularity❌ Poor combinations:├── Last 365 days → Hourly (too many data points)├── Last 24 hours → Monthly (not enough data)
Trodo uses a 30-minute session timeout (not configurable):
Session Definition:├── Session starts: First event from user├── Session continues: Events within 30 min of last event├── Session ends: 30 min of inactivity└── New session: Activity after 30 min gap
For most browser SDK events, timestamps reflect when the client sent the event. If you also send server-side or backend events (for example when a long-running job finishes), those timestamps reflect server clock time. When comparing steps across sources, align on a single notion of “completed” (for example one agent_run_completed from the system of record).
Question: What happened today?Time: Today, hourly granularityQuestion: How are we trending this month?Time: Last 30 days, daily granularityQuestion: Year-over-year growth?Time: Last 365 days, monthly granularity
✅ Good comparisons:├── Week-over-week (similar periods)├── Month-over-month (business rhythm)├── Year-over-year (seasonal adjustment)❌ Poor comparisons:├── Monday vs Sunday (different behavior)├── Holiday vs normal week (outliers)├── Launch week vs normal (unusual activity)
If analyzing "Today":├── Events appear in real-time├── Transactions may have confirmation lag├── Some aggregations update hourlyRecommendation: Use "Yesterday" for complete daily data