Known Limitations & Edge Cases

Delayed Events (2-3 minutes)

Data is not real-time. Events are batched and buffered for performance. Typical delay is 30 seconds to 2 minutes from the user opening the app. If a customer says "I just logged in but don't see it," tell them to wait 2-3 minutes and refresh. This is expected behavior.

Mobile App

Native mobile apps (iOS/Android) are NOT tracked for login activity. GoCSM tracks feature adoption and revenue intelligence through the mobile app, but login activity specifically relies on browser-based login events.

Historical Data Limits (180 days)

Data is retained for a maximum of 6 months. "Last Year" or "Year-to-Date" options are NOT available if they exceed this window.

Bot Traffic Inflation

Automated testing tools (Selenium, Puppeteer) that load the web UI may inflate login counts. Look for suspiciously regular patterns or 24/7 activity. Workaround: Exclude specific user IDs from tracking.

No Device/Browser Breakdown

We do NOT track device type, browser, operating system, or User-Agent. This is a deliberate privacy-first design decision.

Session Refresh Behavior

If a user keeps a tab open for hours but doesn't interact, we do NOT count it as "active time." Tracking stops when the tab is hidden or idle for 5 minutes.