-
Notifications
You must be signed in to change notification settings - Fork 116
feat(): update ltv client references to new new profile clients #7728
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?
feat(): update ltv client references to new new profile clients #7728
Conversation
LEFT JOIN | ||
`moz-fx-data-shared-prod.fenix.client_adclicks_history` | ||
USING (sample_id, client_id) | ||
WHERE | ||
-- BrowserStack clients are bots, we don't want to accidentally report on them | ||
first_reported_isp != "BrowserStack" | ||
app_name <> "Fenix BrowserStack" |
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.
Should we also be exluding Mozilla Online
here @kwindau ?
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.
I think we are only excluding BrowserStack due to bots, not due to DAU definitions (this is more LTV focused than DAU focused). I think it's ok to leave as is, thanks for checking
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.
@kwindau one more question, is there a use case where we may want to look at this data and filter out Mozilla Online users?
c.first_reported_isp | ||
clients.adjust_network, | ||
clients.country AS first_reported_country, | ||
CAST(NULL AS STRING) AS first_reported_isp, |
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.
isp
field no longer available. As far as I recall the only purpose we used it for was to identify bots. This is now done upstream and this filtering can be done via app_name
@@ -2,7 +2,7 @@ fields: | |||
- name: client_id | |||
mode: NULLABLE | |||
type: STRING | |||
description: "Client ID; uniquely identifies a client. Joinable with fenix.firefox_android_clients." | |||
description: "Client ID; uniquely identifies a client." |
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.
Removed the last part since it's joinable with anything on client_id.
Integration report for "feat: update firefox_ios_references in firefox ios ltv to use new_profile_clients"
|
feat(): update ltv client references to new new profile clients
This is work towards deprecating firefox_ios_clients and firefox_android_clients