-
Notifications
You must be signed in to change notification settings - Fork 105
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
MC-1608 Add job for New Tab engagement by corpus_item_id #6743
Open
mmiermans
wants to merge
7
commits into
main
Choose a base branch
from
MC-1608-newtab-merino-corpus-items
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+53
−18
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mmiermans
force-pushed
the
MC-1608-newtab-merino-corpus-items
branch
2 times, most recently
from
January 2, 2025 14:22
8ac9083
to
79804ce
Compare
This comment has been minimized.
This comment has been minimized.
This job is similar to bqetl_merino_newtab_extract_to_gcs, but it aggregates on corpus_item_id instead of scheduled_corpus_item_id. The latter (as the name implies) identifies a scheduled item. We want to start aggregating on the item itself because we will stop scheduling them for specific dates as part of an experiment in Q1.
mmiermans
force-pushed
the
MC-1608-newtab-merino-corpus-items
branch
from
January 2, 2025 14:58
f271ea5
to
f26af98
Compare
This comment has been minimized.
This comment has been minimized.
Integration report for "Merge branch 'main' into MC-1608-newtab-merino-corpus-items"
|
5 tasks
chelseybeck
approved these changes
Jan 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds a column
corpus_item_id
to the New Tab engagement data consumed by Merino.The job will continue to aggregate on
scheduled_corpus_item_id
. A scheduled corpus item is an item that was scheduled on a particular date. In Q1, we will start recommending some items that have not been scheduled for a particular date, and therefore do not have ascheduled_corpus_item_id
. We want to aggregate clicks and impressions both bycorpus_item_id
and byscheduled_corpus_item_id
. In the backend, everyscheduled_corpus_item_id
maps to exactly onecorpus_item_id
. In the Glean data,corpus_item_id
is often null because we only start emitting it from Firefox Desktop >= 134.QA
Below is an analysis of the results before and after the changes in the PR.
✅ Engagement metrics remain similar
There aren't yet any recommendations on New Tab that don't have a scheduled_corpus_item_id. As expected, engagement before and after are very similar. Small differences in clicks and impressions are expected because the live table is queried.
scheduled_corpus_item_id
region
✅ There is good coverage of
corpus_item_id
The vast majority of rows and the items that are seen on New Tab will have a corpus_item_id.
corpus_item_id
corpus_item_id
corpus_item_id
Related Tickets & Documents
Reviewer, please follow this checklist