Skip to content
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

Issue with first_seen_date field in fenix.new_profile_activation #5192

Open
irrationalagent opened this issue Mar 10, 2024 · 1 comment
Open

Comments

@irrationalagent
Copy link
Collaborator

irrationalagent commented Mar 10, 2024

I noticed this for Jan 2024, but other dates could be affected as well. There are no clients with first_seen_date for:

  • 2024-01-02
  • 2024-01-04 to 2024-01-07 inclusive
  • 2024-01-12

query

There may be other dates affected, I only noticed for jan 2024. There seems to be a normalish amount of rows for each date partition for the above days.

This table is joined to android marketing metrics in looker to power the Google UAC Android campaign activation explore. That's where I initially noticed the problem.

┆Issue is synchronized with this Jira Task

@data-sync-user
Copy link
Collaborator

➤ Leif Oines commented:

Arguably, for the looker explore linked above we should be using firefox_android_clients as the source table for new profiles. However, if we still want to report on activations, we would still need to incorporate new_profile_activation in some way (or compute the activations separately somehow).

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

No branches or pull requests

2 participants