Skip to content

chore(analytics): clarify squad analytics tiles are lifetime - #6696

Merged
idoshamun merged 1 commit into
mainfrom
chore/squad-analytics-lifetime-labels
Sep 21, 2026
Merged

idoshamun merged 1 commit into
mainfrom
chore/squad-analytics-lifetime-labels

Conversation

@idoshamun

@idoshamun idoshamun commented Sep 21, 2026

Copy link
Copy Markdown
Member

Summary

Follow-up to #6691, same fix on the squad analytics page:

  • ImpressionsLifetime impressions
  • Unique reachLifetime reach
  • Both tooltips now say "lifetime" explicitly.
  • Dropped (last 45 days) from the Discovery and Engagement headers — those numbers were never windowed.
  • Moved the window to where it actually applies: Impressions over time (last 45 days).

Why

squadAnalytics is backed by the squad_posts_analytics materialized view, which is a plain SUM over post_analytics per sourceId with no time filter — impressions, reach and every engagement number on this page are cumulative. Only the chart is windowed (HISTORY_LIMIT = 45), so that is the only place the "last 45 days" wording belongs.

Note "lifetime" means since 2025-08-25, when the ClickHouse post analytics pipeline started collecting.

Still outstanding: /analytics (author dashboard) has the same wrong "Overview (last 45 days)" header over user_posts_analytics.

🤖 Opened by Smith on behalf of @idoshamun

Preview domain

https://chore-squad-analytics-lifetime-l.preview.app.daily.dev

@vercel

vercel Bot commented Sep 21, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
daily-webapp Ready Ready Preview Sep 21, 2026 2:54pm UTC

Request Review

@idoshamun
idoshamun merged commit 073d896 into main Sep 21, 2026
11 checks passed
@idoshamun
idoshamun deleted the chore/squad-analytics-lifetime-labels branch September 21, 2026 14:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant