Average Scroll Depth Metric: another imported schema migration #4932
+21
−0
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
|
Is this for importing data from another Plausible instance, GA4, or both? |
Only for importing from another Plausible instance. |
ukutaht
approved these changes
Jan 2, 2025
RobertJoonas
deleted the
scroll-depth-imported-pageleave-visitors-migration
branch
4 tasks
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.
Changes
When merging imported data into stats queries, we cannot simply divide
scroll_depth/visitorsto get the imported scroll depth. That’s wrong becausevisitorsis based on pageviews, not pageleaves. Therefore, we’ll need to export an additional metric -pageleave_visitorswhich we can use specifically for that calculation.Note: This field should also be used for our new time on page in the future
Tests
Changelog
Documentation
Dark mode