-
Notifications
You must be signed in to change notification settings - Fork 124
feat(DEN-9914) Create hourly table for Onboarding data #8584
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
This comment has been minimized.
This comment has been minimized.
sql/moz-fx-data-shared-prod/firefox_desktop_derived/onboarding_hourly_v2/metadata.yaml
Outdated
Show resolved
Hide resolved
sql/moz-fx-data-shared-prod/firefox_desktop_derived/onboarding_hourly_v2/query.sql
Outdated
Show resolved
Hide resolved
sql/moz-fx-data-shared-prod/firefox_desktop_derived/onboarding_hourly_v2/query.sql
Show resolved
Hide resolved
sql/moz-fx-data-shared-prod/firefox_desktop_derived/onboarding_hourly_v2/schema.yaml
Show resolved
Hide resolved
Integration report for "change expiration date to only 7 days"
|
sean-rose
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
r+wc
| owner: [email protected] | ||
| retries: 1 | ||
| retry_delay: 10m | ||
| start_date: '2025-12-10' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion (non-blocking): With catchup enabled this would trigger >48 hourly DAG runs over the past three days, so you might want to adjust the start date to today.
| start_date: '2025-12-10' | |
| start_date: '2025-12-12' |
Description
This PR adds an hourly view for the
firefox_desktop.onboardingdata. The growth PMs would like an hourly view. An hourly run would let them check key metrics (impressions, clicks, dismissals) same-day instead of next-day, making it feasible to adjust copy/targeting before users churn. Waiting ~24 h is slowing the feedback loop and decision-making.Related Tickets & Documents
Reviewer, please follow this checklist