We've improved the accuracy of Signals metrics calculations to better match legacy system values.
Fixes
- Frequency Filtering: Added proper frequency filtering to benchmarking endpoints (Acquisition, Engagement, Enlistment tabs) to prevent double-counting from both daily and monthly data rows
- API Source Handling: Fixed case-insensitive comparison for API source preference (quest vs fury), ensuring consistent data selection regardless of database capitalization
- Simplified Data Processing: Streamlined the legacy metric loading pipeline for more predictable results
Technical Details
- Benchmarking routes now properly filter:
uniqueVisitorsandavgMinutesToFirstReplyuse monthly frequency, all other metrics use daily frequency - API source preference correctly handles variations like 'Quest', 'QUEST', 'quest'
These improvements ensure your Benchmark Comparison and Benchmarking tabs display accurate metrics that align with historical data.