Change epic view tracking threshold back to 0#15267
Merged
Conversation
tomrf1
added
fix
AnastasiiaBalenko
approved these changes
Feb 2, 2026
sookburt
approved these changes
Feb 2, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
We use the VIEW event in the datalake for measuring performance of epic variants, for £LTV3/impression.
A previous change set the VIEW event threshold for the epic at 40%.
We've now decided this is not desirable.
This has created the potential for invalid epic tests where a variant has fewer users scrolling to 40%. This can mean the variant has a lower £/INSERT but a higher £/VIEW, incorrectly making it the winner.
This PR changes the threshold back to 0 for the VIEW event.
It also adds a new view tracker, at 40%, for the epic view record in browser storage. This is used for limiting how many epics a user sees per month, and we still want this to be 40%.
Tested in CODE by observing the ophan VIEW event being sent at the top of the epic, and the local storage item (
gu.contributions.views) updating part way down it.